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

Job configure - properties will be deleted

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Open (View Workflow)
    • Priority: Major
    • Resolution: Unresolved
    • Component/s: _unsorted
    • Labels:
    • Environment:
      Jenkins verson 2.267
    • Similar Issues:

      Description

      After update from jenkins version 2.263 to 2.267 and update of all plugins it seems everything is fine.

       

      But if you change anything in an existing pipeline job, like increasig number of Max # of builds to keep in Discard old builds, and save the changes there, all properties will be deleted.

      Just the the configuration of the pipeline stage is there.

      I can reproduce this with each propertie in the pipeline job. It affected all general properties and build trigger properties.

       

      There is also a second behaviour. If you change a property in the pipeline script, it is not possible to save the pipeline job.

       

      One of this 2 scenarios will be entered. 

       

      After downgrade of jenkins version it is working again. (plugins will not be downgraded)

        Attachments

          Issue Links

            Activity

            Hide
            sminster Scott Minster added a comment -

            Any updates on this issue?  I recently upgraded a Jenkins install to 2.277.2 and am experiencing the same thing in pipeline jobs.  They work fine, but modifying them results in all configuration values being lost.  Looking in the config.xml file, it looks like things that were in the <properties> tag are not being written out.  This doesn't appear to affect freestyle job types.

            Perhaps there is some kind of conflict between the workflow-job plugin and Jenkins that is causing the properties to be lost when saving?

            Show
            sminster Scott Minster added a comment - Any updates on this issue?  I recently upgraded a Jenkins install to 2.277.2 and am experiencing the same thing in pipeline jobs.  They work fine, but modifying them results in all configuration values being lost.  Looking in the config.xml file, it looks like things that were in the <properties> tag are not being written out.  This doesn't appear to affect freestyle job types. Perhaps there is some kind of conflict between the workflow-job plugin and Jenkins that is causing the properties to be lost when saving?
            Hide
            sminster Scott Minster added a comment -

            Replying to myself because I found an update: JENKINS-64241 documents a problem with the Team Foundation Server plugin that is causing this issue.  When I disabled that plugin (I wasn't using it) in my Jenkins installation, the problem went away.

            Show
            sminster Scott Minster added a comment - Replying to myself because I found an update: JENKINS-64241 documents a problem with the Team Foundation Server plugin that is causing this issue.  When I disabled that plugin (I wasn't using it) in my Jenkins installation, the problem went away.
            Hide
            markewaite Mark Waite added a comment -

            Scott Minster you're reporting a very different problem than is described in this issue. This issue is reporting a problem that existed before the configuration form modernization of Jenkins 2.277.1. The problem you're encountering is specifically related to the changes in Jenkins 2.277.1 and later.

            You can read about the configuration form modernization in the changelog and the upgrade guide. You can watch the Jenkins 2.277.1 webinar for more details on the changes.

            Show
            markewaite Mark Waite added a comment - Scott Minster you're reporting a very different problem than is described in this issue. This issue is reporting a problem that existed before the configuration form modernization of Jenkins 2.277.1. The problem you're encountering is specifically related to the changes in Jenkins 2.277.1 and later. You can read about the configuration form modernization in the changelog and the upgrade guide . You can watch the Jenkins 2.277.1 webinar for more details on the changes.
            Hide
            whitingjr Jeremy Whiting added a comment -

             Like Scott Minster I'm seeing similar behaviour described in this issue but using 2.277.2 and no Team Foundation Server.

            Mark Waite do you suggest a separate issue be created for the 2.277.2 version to be associated more closely with XStream changes ?

            Show
            whitingjr Jeremy Whiting added a comment -  Like Scott Minster I'm seeing similar behaviour described in this issue but using 2.277.2 and no Team Foundation Server. Mark Waite do you suggest a separate issue be created for the 2.277.2 version to be associated more closely with XStream changes ?
            Hide
            markewaite Mark Waite added a comment - - edited

            Jeremy Whiting I suspect that the issue you're seeing is related to configuration form modernization rather than XStream changes. I don't recall the last time we found an issue related to XStream changes. Yes, a separate issue is preferred, after you've performed the configuration form modernization upgrade steps.

            Configuration form modernization investigations usually follow this pattern:

            Steps you can take to help yourself and help us help you

            Show
            markewaite Mark Waite added a comment - - edited Jeremy Whiting I suspect that the issue you're seeing is related to configuration form modernization rather than XStream changes. I don't recall the last time we found an issue related to XStream changes. Yes, a separate issue is preferred, after you've performed the configuration form modernization upgrade steps. Configuration form modernization investigations usually follow this pattern: Steps you can take to help yourself and help us help you Follow the instructions in the Jenkins 2.277.1 upgrade guide , the Jenkins 2.277.1 changelog , and the Jenkins 2.277.1 webinar and its slides Remove unused plugins from your installation Remove deprecated plugins from your installation (like DRY, checkstyle, warnings, ...) Remove plugins with security issues from your installation (like TFS, ...) Update plugins to the latest releases Remove plugins with known issues in config form modernization Confirm that the issue is still visible Provide the information requested in "How to report an issue" , especially including the specific details : Jenkins version Jenkins plugin names and versions (please report with the format provided by the script )
            Hide
            whitingjr Jeremy Whiting added a comment - - edited

            Mark Waite thanks for the process. I've already been through and followed the suggested steps. I created JENKINS-65684 as suggested.

             

            Show
            whitingjr Jeremy Whiting added a comment - - edited Mark Waite thanks for the process. I've already been through and followed the suggested steps. I created JENKINS-65684 as suggested.  
            Hide
            whitingjr Jeremy Whiting added a comment -

            Scott Minster if you are using the JMS Plugin then take a look at JENKINS-65684.

            Show
            whitingjr Jeremy Whiting added a comment - Scott Minster if you are using the JMS Plugin then take a look at JENKINS-65684 .

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              hausthom29 Thomas Hauser
              Votes:
              2 Vote for this issue
              Watchers:
              5 Start watching this issue

                Dates

                Created:
                Updated: