• Type: Bug
• Resolution: Fixed
• Priority: Minor
• Component/s: build-pipeline-plugin
• Labels:

  None
• Environment:

  Jenkins 1.609.3
  Build Pipeline v1.4.7

1. 

   screenshot-1.png

   92 kB

   2015-10-06 13:15

[JENKINS-30404] Run button not clickable with parameterized builds

Renaud Lehoux created issue - 2015-09-11 10:38

Renaud Lehoux made changes - 2015-09-11 10:38

Link

New: This issue is related to JENKINS-20873 [ JENKINS-20873 ]

Collapse comment: Idan Bidani added a comment - 2015-09-18 02:16

Idan Bidani added a comment - 2015-09-18 02:16

Did you mean Jenkins version 1.609.3? there was no release with version 1.606.3

Expand comment: Idan Bidani added a comment - 2015-09-18 02:16

Idan Bidani added a comment - 2015-09-18 02:16 Did you mean Jenkins version 1.609.3? there was no release with version 1.606.3

Collapse comment: Renaud Lehoux added a comment - 2015-09-22 10:50

Renaud Lehoux added a comment - 2015-09-22 10:50

idanatcox You are right, I meant 1.609.3.

Expand comment: Renaud Lehoux added a comment - 2015-09-22 10:50

Renaud Lehoux added a comment - 2015-09-22 10:50 idanatcox You are right, I meant 1.609.3.

Renaud Lehoux made changes - 2015-09-22 10:50

Environment

Original: Jenkins 1.606.3 Build Pipeline v1.4.7

New: Jenkins 1.609.3 Build Pipeline v1.4.7

Renaud Lehoux made changes - 2015-09-22 10:51

Description

Original: The run button is not clickable when the first job of the pipeline is parameterized. A similar bug has already been opened and fixed a few years ago [here|https://issues.jenkins-ci.org/browse/JENKINS-20873], but I still have the same problem with the current version. Please not that this new problem was also mentioned by [~barbarello] in a [recent comment|https://issues.jenkins-ci.org/browse/JENKINS-20873?focusedCommentId=231041&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-231041].

New: The run button is not clickable when the first job of the pipeline is parameterized. A similar bug has already been opened and fixed a few years ago [here|https://issues.jenkins-ci.org/browse/JENKINS-20873], but I still have the same problem with the current version. Please not that this new problem was also mentioned by [~barbarello] in a [recent comment|https://issues.jenkins-ci.org/browse/JENKINS-20873?focusedCommentId=231041&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-231041].

Martin d'Anjou made changes - 2015-10-06 13:15

Attachment

New: screenshot-1.png [ 30797 ]

Collapse comment: Dan Alvizu added a comment - 2016-02-16 17:48

Dan Alvizu added a comment - 2016-02-16 17:48

Are you running behind a proxy? Do you have Jenkins URL set in global config?

Expand comment: Dan Alvizu added a comment - 2016-02-16 17:48

Dan Alvizu added a comment - 2016-02-16 17:48 Are you running behind a proxy? Do you have Jenkins URL set in global config?

Collapse comment: Leif Rilbe added a comment - 2016-05-26 05:53, Edited by Leif Rilbe - 2016-05-26 06:46

Leif Rilbe added a comment - 2016-05-26 05:53 - edited

I also have the same issue with the run button.

Is there a workaround? If not, I think that this is not a "minor" issue, but rather a "critical" one.

Hm.. after upgrade to Jenkins 1.651.2 the build button now works. So, it seems it was a version compatibility issue maybe...

Expand comment: Leif Rilbe added a comment - 2016-05-26 05:53, Edited by Leif Rilbe - 2016-05-26 06:46

Leif Rilbe added a comment - 2016-05-26 05:53 - edited I also have the same issue with the run button. Is there a workaround? If not, I think that this is not a "minor" issue, but rather a "critical" one. Hm.. after upgrade to Jenkins 1.651.2 the build button now works. So, it seems it was a version compatibility issue maybe...

Leif Rilbe made changes - 2016-05-26 06:11

Priority

Original: Minor [ 4 ]

New: Critical [ 2 ]

Load more newer events