Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. 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.

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • maven-plugin
    • 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.

          Tony Bridges added a comment -

          I have the same issue in the postbuild step. When we upgraded from 1513 to 1517, the values reset themselves to "use default maven settings" and we cannot change them back to use the managed settings file that administers our repository credentials.
          Has anyone made progress on this issue ? It's a significant regression.

          Tony Bridges added a comment - I have the same issue in the postbuild step. When we upgraded from 1513 to 1517, the values reset themselves to "use default maven settings" and we cannot change them back to use the managed settings file that administers our repository credentials. Has anyone made progress on this issue ? It's a significant regression.

          Andreas Horst added a comment -

          I can confirm this on 1.522.

          Andreas Horst added a comment - I can confirm this on 1.522.

          Confirmed on LTS 1.509.4
          It's funny this bug has been introduced as a "fix" to a LTS Release

          David Fuenmayor added a comment - Confirmed on LTS 1.509.4 It's funny this bug has been introduced as a "fix" to a LTS Release

            Unassigned Unassigned
            drb9764 David Barber
            Votes:
            3 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: