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?

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.

sminster 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.

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

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

whitingjr 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)

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

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