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

Upgrading to 2.267 broke Pipeline configuration saving

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      In pipeline configuration option:
       
      This project is parameterized: Global Variable String Parameter can't be set. It is saying 
      Global Variable  does not exist - eventhouht I can select it from drop down and confirmed that it exists

      Second issue:
      It is not saving Build periodically option any longer: H/60 * * * *
      Actually I can save it but, when i open for edit again - it is not showing and build it not triggered automatically as it used to be before upgrade. I can't downgrade back, as seems like configuration cannot be restored or recreated again
       
      After saving everything is blank. No option can be saved
       

        Attachments

          Issue Links

            Activity

            Hide
            timja Tim Jacomb added a comment -

            likely related to https://issues.jenkins.io/browse/JENKINS-64241, can you reproduce this when the TFS plugin is disabled / uninstalled?

            Show
            timja Tim Jacomb added a comment - likely related to https://issues.jenkins.io/browse/JENKINS-64241 , can you reproduce this when the TFS plugin is disabled / uninstalled?
            Hide
            gustm80 Gustav Moelschl added a comment -

            I've noticed the same issue when updating to Jenkins 2.264 or later.

            Tested with Jenkins 2.277 and a simple pipeline job:
            If TFS plugin is installed and any SCM trigger is configured, the trigger is lost after saving the job configuration.
            Once the TFS plugin is uninstalled, the problem is gone.

            Attached "PluginList_2021-01-27.txt"

            Show
            gustm80 Gustav Moelschl added a comment - I've noticed the same issue when updating to Jenkins 2.264 or later. Tested with Jenkins 2.277 and a simple pipeline job: If TFS plugin is installed and any SCM trigger is configured, the trigger is lost after saving the job configuration. Once the TFS plugin is uninstalled, the problem is gone. Attached "PluginList_2021-01-27.txt"
            Hide
            isalo Ivan Salo added a comment -

            yes, uninstalling TFS plugin resolved this issue.

            Thanks for workaround.

            Show
            isalo Ivan Salo added a comment - yes, uninstalling TFS plugin resolved this issue. Thanks for workaround.

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              isalo Ivan Salo
              Votes:
              1 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: