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

Perform Maven release screen should not autorefresh

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Minor Minor
    • m2release-plugin
    • None

      If "Auto Refresh" is on the Perform Maven Release screen is difficult to operate because it keeps losing custom values entered for SCM login/password when the screen refreshes. I don't think that this screen should be an auto refresh screen.

      I've tested/attached a patch that turns off the auto refresh. I did the test against an m2 release plugin checkout taken just before the recent java.net changes.

        1. 101213_m2release_action.patch
          0.8 kB

          [JENKINS-8293] Perform Maven release screen should not autorefresh

          Richard Mortimer created issue -

          James Nord added a comment -

          Fix applied. Thanks for the report & patch.

          James Nord added a comment - Fix applied. Thanks for the report & patch.

          James Nord added a comment -

          Fixed in http://ci.jenkins-ci.org/job/plugins_m2release/27/
          by https://github.com/jenkinsci/m2release-plugin/commit/384c6104cf1ad8e8c2b399e998bccdaeaae35d92

          James Nord added a comment - Fixed in http://ci.jenkins-ci.org/job/plugins_m2release/27/ by https://github.com/jenkinsci/m2release-plugin/commit/384c6104cf1ad8e8c2b399e998bccdaeaae35d92
          James Nord made changes -
          Resolution New: Fixed [ 1 ]
          Status Original: Open [ 1 ] New: Resolved [ 5 ]
          James Nord made changes -
          Status Original: Resolved [ 5 ] New: Closed [ 6 ]
          R. Tyler Croy made changes -
          Workflow Original: JNJira [ 138403 ] New: JNJira + In-Review [ 204760 ]
          James Nord made changes -
          Assignee Original: James Nord [ teilo ]

            Unassigned Unassigned
            oldelvet Richard Mortimer
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: