Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-11004

Alternate settings file configuration cleared after editing job

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Major Major
    • maven-plugin
    • None

      Steps to reproduce:
      1) Define new or edit and save existing maven 2/3 build job which uses alternate settings.xml file
      2) Have Jenkins run that job (this step at finish clears configured alternate settings.xml of the project)
      3) Every next build fails - editing build job shows that alternate settings.xml is cleared

      Following commit is likely cause: https://github.com/jenkinsci/jenkins/commit/a254f202f971497a277f758cae5de84292073a4d so bug is there since 1.426

          [JENKINS-11004] Alternate settings file configuration cleared after editing job

          Steve Roth added a comment -

          me too. I have seen this when removing a view. It appeared that the view was removed, but the view removal was not persisted to the Jenkins config file, so on a subsequent restart the view re-appeared.

          Note that there seems to be some path or time delay (which I havent quite identified) by which the update eventually is persisted, but if you make a change and immediately restart Jenkins, it definitely was not (in my experience).

          Steve Roth added a comment - me too. I have seen this when removing a view. It appeared that the view was removed, but the view removal was not persisted to the Jenkins config file, so on a subsequent restart the view re-appeared. Note that there seems to be some path or time delay (which I havent quite identified) by which the update eventually is persisted, but if you make a change and immediately restart Jenkins, it definitely was not (in my experience).

          Dan Rollo added a comment -

          I'm seeing the same problem in v1.431. It seems the "Alternate Settings file" value is never repopulated into the config screen. Therefore, when you re-save, any existing value is cleared (since the screen was not populated with the existing value).

          Dan Rollo added a comment - I'm seeing the same problem in v1.431. It seems the "Alternate Settings file" value is never repopulated into the config screen. Therefore, when you re-save, any existing value is cleared (since the screen was not populated with the existing value).

          Stevo Slavić added a comment -

          This is duplicate of JENKINS-10955

          Stevo Slavić added a comment - This is duplicate of JENKINS-10955

            olamy Olivier Lamy
            sslavic Stevo Slavić
            Votes:
            9 Vote for this issue
            Watchers:
            10 Start watching this issue

              Created:
              Updated:
              Resolved: