-
Bug
-
Resolution: Fixed
-
Major
-
None
After upgrading a recent Hudson installation to 1.352, I'm unable to use an alternate settings.xml file. See the log:
—
<===[HUDSON REMOTING CAPACITY]===>channel started
Executing Maven: -B -f c:\hudson-slave\workspace\my-job-name\pom.xml -s ../wde/config/maven/settings.xml clean install -X
WARNING: Alternate user settings file: ../wde/config/maven/settings.xml is invalid. Using default path.
—
Please note that I want to use the file that exists at:
c:\wde\config\maven\settings.xml
So, I have configured the field 'Alternate settings file' to have this value:
../../../wde/config/maven/settings.xml
The help text says that 'This path is relative to the workspace root.'
I guess the workspace root in my case is:
c:\hudson-slave\workspace\my-job-name\
So, '../../../' would strip 3 directories, leading us to just 'c:'
The issue also exists on version 1.351
- depends on
-
JENKINS-5627 Maven alternative settings seems confused about the structure of the workspace
-
- Resolved
-
- duplicates
-
JENKINS-4693 Alternate settings file not found
-
- Reopened
-
[JENKINS-6080] Unable to use alternate settings file after upgrading to Hudson 1.352
Link |
New:
This issue depends on |
Description |
Original:
After upgrading a recent Hudson installation to 1.352, I receive this error message: WARNING: Alternate user settings file: ../wde/config/maven/settings.xml is invalid. Using default path. |
New:
After upgrading a recent Hudson installation to 1.352, I receive this error message: WARNING: Alternate user settings file: ../wde/config/maven/settings.xml is invalid. Using default path. The issue also exists on version 1.351 |
Link | New: This issue duplicates JENKINS-4693 [ JENKINS-4693 ] |
Description |
Original:
After upgrading a recent Hudson installation to 1.352, I receive this error message: WARNING: Alternate user settings file: ../wde/config/maven/settings.xml is invalid. Using default path. The issue also exists on version 1.351 |
New:
After upgrading a recent Hudson installation to 1.352, I'm unable to use an alternate settings.xml file. See the log: --- <===[HUDSON REMOTING CAPACITY]===>channel started Executing Maven: -B -f c:\hudson-slave\workspace\my-job-name\pom.xml -s ../wde/config/maven/settings.xml clean install -X WARNING: Alternate user settings file: ../wde/config/maven/settings.xml is invalid. Using default path. --- Please note that I want to use the file that exists at: c:\wde\config\maven\settings.xml The issue also exists on version 1.351 |
Description |
Original:
After upgrading a recent Hudson installation to 1.352, I'm unable to use an alternate settings.xml file. See the log: --- <===[HUDSON REMOTING CAPACITY]===>channel started Executing Maven: -B -f c:\hudson-slave\workspace\my-job-name\pom.xml -s ../wde/config/maven/settings.xml clean install -X WARNING: Alternate user settings file: ../wde/config/maven/settings.xml is invalid. Using default path. --- Please note that I want to use the file that exists at: c:\wde\config\maven\settings.xml The issue also exists on version 1.351 |
New:
After upgrading a recent Hudson installation to 1.352, I'm unable to use an alternate settings.xml file. See the log: --- <===[HUDSON REMOTING CAPACITY]===>channel started Executing Maven: -B -f c:\hudson-slave\workspace\my-job-name\pom.xml -s ../wde/config/maven/settings.xml clean install -X WARNING: Alternate user settings file: ../wde/config/maven/settings.xml is invalid. Using default path. --- Please note that I want to use the file that exists at: c:\wde\config\maven\settings.xml So, I have configured the field 'Alternate settings file' to have this value: ../../../wde/config/maven/settings.xml the help text says that 'This path is relative to the workspace root.' I guess the workspace root in my case is: c:\hudson-slave\workspace\my-job-name\ So, '../../../' would strip 3 directories, leading us to just 'c:' The issue also exists on version 1.351 |
Component/s | New: master-slave [ 15489 ] | |
Description |
Original:
After upgrading a recent Hudson installation to 1.352, I'm unable to use an alternate settings.xml file. See the log: --- <===[HUDSON REMOTING CAPACITY]===>channel started Executing Maven: -B -f c:\hudson-slave\workspace\my-job-name\pom.xml -s ../wde/config/maven/settings.xml clean install -X WARNING: Alternate user settings file: ../wde/config/maven/settings.xml is invalid. Using default path. --- Please note that I want to use the file that exists at: c:\wde\config\maven\settings.xml So, I have configured the field 'Alternate settings file' to have this value: ../../../wde/config/maven/settings.xml the help text says that 'This path is relative to the workspace root.' I guess the workspace root in my case is: c:\hudson-slave\workspace\my-job-name\ So, '../../../' would strip 3 directories, leading us to just 'c:' The issue also exists on version 1.351 |
New:
After upgrading a recent Hudson installation to 1.352, I'm unable to use an alternate settings.xml file. See the log: --- <===[HUDSON REMOTING CAPACITY]===>channel started Executing Maven: -B -f c:\hudson-slave\workspace\my-job-name\pom.xml -s ../wde/config/maven/settings.xml clean install -X WARNING: Alternate user settings file: ../wde/config/maven/settings.xml is invalid. Using default path. --- Please note that I want to use the file that exists at: c:\wde\config\maven\settings.xml So, I have configured the field 'Alternate settings file' to have this value: ../../../wde/config/maven/settings.xml The help text says that 'This path is relative to the workspace root.' I guess the workspace root in my case is: c:\hudson-slave\workspace\my-job-name\ So, '../../../' would strip 3 directories, leading us to just 'c:' The issue also exists on version 1.351 |
Component/s | Original: master-slave [ 15489 ] |
See JENKINS-4693 - we fixed the logic for relative paths to alternate settings files, and you may need to update your paths to fit this.