-
Bug
-
Resolution: Unresolved
-
Major
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.
This occurs all the way up to the latest version (1.3.3).
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
Have you tried using the 1.3.4-SNAPSHOT version? We are using it just to make Manual Parameterized builds available. Bugs on rerun, but otherwise works. Haven't tested on Parameterized downstream project though.
But I would much like that a 1.3.4 version was commited with current code all the same.