-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
Jenkins 1.515 in Centos 6.
After upgrading Jenkins from version 1.513 to 1.515, I cannot save the field Settings file to "Settings file in filesystem" which is pointed to a local settings.xml file for the maven (Invoke top-level Maven target) prebuild step. It will let me enter all the information and save it but it is not permanently saved in the job's config.xml file. When I reconfigure the job, the Settings file defaults back to "use default maven settings". The workaround is to the "-s" parameter to the Goals field. This is annoying because we have many jenkins jobs that use "Invoke top-level Maven target" as a prebuild step.
[JENKINS-18183] After upgrading from jenkins 1.513 to 1.515, I cannot use Settings file (Settings file in filesystem) field in a maven prebuild step for a maven project.
David Barber
created issue -
David Barber
made changes -
| Description | Original: After upgrading Jenkins from version 1.513 to 1.515, I cannot save the field Settings file to "Settings file in filesystem" which is pointed to a local settings.xml file for the maven (Invoke top-level Maven target) prebuild step. It will let me enter all the information and save it but it is not permanently saved in the job's config.xml file. When I reconfigure the job, the Settings file defaults back to "use default maven settings". The workaround is to the "-s" parameter to the Goals field. This is annoying because have many jenkins jobs that use "Invoke top-level Maven target" as a prebuild step. | New: After upgrading Jenkins from version 1.513 to 1.515, I cannot save the field Settings file to "Settings file in filesystem" which is pointed to a local settings.xml file for the maven (Invoke top-level Maven target) prebuild step. It will let me enter all the information and save it but it is not permanently saved in the job's config.xml file. When I reconfigure the job, the Settings file defaults back to "use default maven settings". The workaround is to the "-s" parameter to the Goals field. This is annoying because we have many jenkins jobs that use "Invoke top-level Maven target" as a prebuild step. |
David Barber
made changes -
| Summary | Original: After upgrading from jenkins 1.513 to 1.5.15, I cannot use Settings file (Settings file in filesystem) field in a maven prebuild step for a maven project. | New: After upgrading from jenkins 1.513 to 1.515, I cannot use Settings file (Settings file in filesystem) field in a maven prebuild step for a maven project. |
| Workflow | Original: JNJira [ 149481 ] | New: JNJira + In-Review [ 177379 ] |