-
Bug
-
Resolution: Cannot Reproduce
-
Major
-
None
-
Client:
Windows Vista: IE8, Chrome10, Firefox4
Ubuntu: Firefox 3.6
Server:
Tomcat 7.0.11, jenkins deployed as WAR file.
Trying to add a parameterized parameter to an already existing jenkins job (which already has a couple of parameterized parameters) does not work. When I click on "Add Parameter" drop-down menu and then choose "Choice" (or any other value), nothing happens besides the drop-down menu closing again.
When I last added a parameterized parameter a few weeks ago, it worked like a charm.
Deleting an already existing parameter also seems to work.
- is duplicated by
-
-
- Resolved
-
[JENKINS-9173] Adding a parameterized parameter to a jenkins job does not work
| Environment |
Original:
Windows Vista: IE8, Chrome10, Firefox4 Ubuntu: Firefox 3.6 |
New:
Client: Windows Vista: IE8, Chrome10, Firefox4 Ubuntu: Firefox 3.6 Server: Tomcat 7.0.11, jenkins deployed as WAR file. |
From the changelog from 1.404 it doesn't look like this was fixed. This bug is similar to http://issues.jenkins-ci.org/browse/JENKINS-9142 as it seems that adding any text block to your job configuration doesn't work, whether it's a build step or a parameter. Until this is fixed you can try a little workaround: Create a new job, try adding a parameter, then go back to your old job (without closing your browser) refresh and try adding the parameter again.
Which version of Hudson/Jenkins did you upgrade from?
oseparovic
added a comment - - edited From the changelog from 1.404 it doesn't look like this was fixed. This bug is similar to http://issues.jenkins-ci.org/browse/JENKINS-9142 as it seems that adding any text block to your job configuration doesn't work, whether it's a build step or a parameter. Until this is fixed you can try a little workaround: Create a new job, try adding a parameter, then go back to your old job (without closing your browser) refresh and try adding the parameter again.
Which version of Hudson/Jenkins did you upgrade from? Your workaround worked like a charm, thank you!
The last Jenkins upgrade we performed was from v1.399 to v1.403.
oseparovic
added a comment - Glad to help. Hopefully this will be fixed soon. Also I pointed you to the wrong issue above, my apologies. I've edited that to point to the correct JIRA issue.
oseparovic
added a comment - Glad to help. Hopefully this will be fixed soon. Also I pointed you to the wrong issue above, my apologies. I've edited that to point to the correct JIRA issue. | Link |
New:
This issue is duplicated by |
Jenkins IRC Bot
made changes -
| Component/s | New: core [ 15593 ] | |
| Component/s | Original: parameters [ 15594 ] |
| Resolution | New: Cannot Reproduce [ 5 ] | |
| Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
Just saw that jenkins v1.404 was released yesterday. This bug occurs with v1.403 (our current version), so maybe its already fixed in 1.404. Can anyone check/confirm?