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

regression: Upgrading to 1.528 ("Upgrade Automatically") breaks "configure"

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      When upgrading from 1.527 to 1.528, no jobs can be edited anymore!

      When clicking the configure button (or going to jobname/configure), it starts loading the fields and filling in the data from the configuration, but the "LOADING" overlay never disappears, and the job settings can't be changed.

      When looking at the web browser console, I see a lot of ajax POST requests from the browser, but the LOADING never disappears.

      Downgrading to 1.527 solves the problem.

      Are there any more logs I can attach to help solving the problem?

        Attachments

          Issue Links

            Activity

            Hide
            mwebber Matthew Webber added a comment -

            Daniel Baldo, do you mean 1.527 or 1.537? Please provide a few more details about your plugin environment.

            Show
            mwebber Matthew Webber added a comment - Daniel Baldo, do you mean 1.527 or 1.537? Please provide a few more details about your plugin environment.
            Hide
            dbaldo Daniel Baldo added a comment -

            My version Jenkins is 1.527. See the atached zip file with my environment.

            Show
            dbaldo Daniel Baldo added a comment - My version Jenkins is 1.527. See the atached zip file with my environment.
            Hide
            dbaldo Daniel Baldo added a comment - - edited

            My environment attached.

            Show
            dbaldo Daniel Baldo added a comment - - edited My environment attached.
            Hide
            mwebber Matthew Webber added a comment -

            Daniel, what exactly are you asking?? You say that you are on 1.527. DO you have the problem on that release or not?

            The problem was fixed in 1.531, as far as I know. Did you read the all the comments in this ticket?

            Show
            mwebber Matthew Webber added a comment - Daniel, what exactly are you asking?? You say that you are on 1.527. DO you have the problem on that release or not? The problem was fixed in 1.531, as far as I know. Did you read the all the comments in this ticket?
            Hide
            jglick Jesse Glick added a comment -

            Believed to have been resolved with the fix in JENKINS-19457.

            Show
            jglick Jesse Glick added a comment - Believed to have been resolved with the fix in JENKINS-19457 .

              People

              Assignee:
              bap bap
              Reporter:
              rggjan rggjan
              Votes:
              53 Vote for this issue
              Watchers:
              69 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: