![]() |
|
|
|
|
Issue Type:
|
![Bug]() Bug
|
|
Assignee:
|
Unassigned |
|
Components:
|
build-pipeline |
|
Created:
|
31/May/13 5:15 PM
|
|
Description:
|
Came here through the Build Pipeline plugin issue tracker link. Since the migration from google code, an annoying bug got lost, which I wanted to reinstate here.
There's a problem when reusing a parameterized downstream project in several upstream projects (with manual run trigger). Only the first upstream project successfully invokes the downstream project retaining parameters set using the groovy script workaround. Other invocations leave the parameters empty in the downstream project.
Case in point: 30 application projects, 4 environments to deploy to. With this bug we need to duplicate a deploy script per application (per environment). So instead of 4 deploy scripts, we now have 120 deploy scripts.
Related issues:
https://code.google.com/p/build-pipeline-plugin/issues/detail?id=54
https://code.google.com/p/build-pipeline-plugin/issues/detail?id=53
|
|
Project:
|
Jenkins
|
|
Labels:
|
plugins
|
|
Priority:
|
![Major]() Major
|
|
Reporter:
|
Benny Bottema
|
|
|
|
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
|
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit
https://groups.google.com/groups/opt_out.
