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

Upgrading to 2.267 broke Pipeline configuration saving

XMLWordPrintable

      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
       

        1. PluginList_2021-01-27.txt
          3 kB
        2. image-2020-11-23-12-48-37-342.png
          image-2020-11-23-12-48-37-342.png
          72 kB
        3. image-2020-11-23-12-47-23-264.png
          image-2020-11-23-12-47-23-264.png
          26 kB

          [JENKINS-64286] Upgrading to 2.267 broke Pipeline configuration saving

          Ivan Salo created issue -
          Ivan Salo made changes -
          Summary Original: Upgrading to 2.267 broke main functionality New: Upgrading to 2.267 broke main Build periodically functionality
          Ivan Salo made changes -
          Environment Original: Windows New: Windows, Jenkins 2.267, all latest plugins and versions
          Ivan Salo made changes -
          Component/s New: core [ 15593 ]
          Ivan Salo made changes -
          Component/s New: workflow-job-plugin [ 21716 ]

          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?

          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?
          Tim Jacomb made changes -
          Component/s New: tfs-plugin [ 15521 ]
          Gustav Moelschl made changes -
          Attachment New: PluginList_2021-01-27.txt [ 53892 ]

          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"

          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"

          Ivan Salo added a comment -

          yes, uninstalling TFS plugin resolved this issue.

          Thanks for workaround.

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

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

              Created:
              Updated:
              Resolved: