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

Navigating back, then forward, from a job configuration causes loss of config data

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Critical Critical
    • core
    • Chrome version 27.0.1453.116 on MacOS 10.6.8.

      1. Open a job configuration that has a conditional build step defined in it, with the Chrome browser (Firefox does not show this problem).
      2. Click the back button to navigate away from the config.
      3. Click forward to go back to the config.
      4. The conditional build step settings will be blank/default, but all other job configuration remains correct.

      This is a really nasty bug, I've had a number of users accidentally break their configs without realizing it, because if you save after this happens you lose the conditional build step settings. Luckily the Job Config History plugin makes it easy for us to undo this.

          [JENKINS-18435] Navigating back, then forward, from a job configuration causes loss of config data

          Owen Mehegan added a comment -

          Dominik - checking on your comment, do you know what the problem is?

          Owen Mehegan added a comment - Dominik - checking on your comment, do you know what the problem is?

          No, sorry...

          Dominik Bartholdi added a comment - No, sorry...

          Ryan Hass added a comment - - edited

          It should be noted that this affects global jenkins configurations and will flip bits for boolean values which should be set to true, to false. This also happens on portions of the configuration page which are not rendered, and need to be expanded to see their values. This is a very critical issue.

          My Chrome version is: Version 35.0.1916.114

          Linux x86-64

          Ryan Hass added a comment - - edited It should be noted that this affects global jenkins configurations and will flip bits for boolean values which should be set to true, to false. This also happens on portions of the configuration page which are not rendered, and need to be expanded to see their values. This is a very critical issue. My Chrome version is: Version 35.0.1916.114 Linux x86-64

          Daniel Beck added a comment -

          Could be related to this: https://rm.cloudbees.com/issues/1959

          Daniel Beck added a comment - Could be related to this: https://rm.cloudbees.com/issues/1959

          removing conditional-buildstep, although it happens also with this plugin, it has nothing to do with it but is an issue with jenkins in general

          Dominik Bartholdi added a comment - removing conditional-buildstep, although it happens also with this plugin, it has nothing to do with it but is an issue with jenkins in general

          Daniel Beck added a comment -

          Similar issues affect multiple browsers, so removing Chrome from title.

          Given the number of issues that appear to be duplicates, raising priority.

          Daniel Beck added a comment - Similar issues affect multiple browsers, so removing Chrome from title. Given the number of issues that appear to be duplicates, raising priority.

          Jesse Glick added a comment -

          Lazy-loaded form fragments are added to the DOM by some JavaScript hooks. Probably these are being run on initial page load but not when revisiting a page, and the browser is throwing out the modified DOM.

          Jesse Glick added a comment - Lazy-loaded form fragments are added to the DOM by some JavaScript hooks. Probably these are being run on initial page load but not when revisiting a page, and the browser is throwing out the modified DOM.

          Jesse Glick added a comment -

          I suspect the most appropriate fix is just to add some JS to block the back/forward buttons while on such a page.

          Jesse Glick added a comment - I suspect the most appropriate fix is just to add some JS to block the back/forward buttons while on such a page.

          Ryan Campbell added a comment -

          rsandell has a PR in review for this issue.

          Ryan Campbell added a comment - rsandell has a PR in review for this issue.

          Daniel Beck added a comment -

          Fixed towards 2.15.

          Daniel Beck added a comment - Fixed towards 2.15.

            rsandell rsandell
            owenmehegan Owen Mehegan
            Votes:
            4 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated:
              Resolved: