[JIRA] [build-pipeline] (JENKINS-18162) Parameterized downstream project is missing upstream-set parameters when used by mutliple upstream projects
Benny Bottema commented on JENKINS-18162 Parameterized downstream project is missing upstream-set parameters when used by mutliple upstream projects I looked up the /api/json for two deploy builds of the downstream project and noticed that the parameters are the same despite being triggered by different upstream builds in two separate pipelines. I also noticed the build-pipeline plugin modified the publishers/ tag of the downstream project during the first deploy build, but with the second the publisher tag is left unmodified. In effect, the downstream project deployed the same application twice. 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.
[JIRA] [build-pipeline] (JENKINS-18162) Parameterized downstream project is missing upstream-set parameters when used by mutliple upstream projects
Benny Bottema edited a comment on JENKINS-18162 Parameterized downstream project is missing upstream-set parameters when used by mutliple upstream projects In an older Jenkins version (1.486) I looked up the /api/json for two deploy builds of the downstream project and noticed that the parameters are the same despite being triggered by different upstream builds in two separate pipelines. I also noticed the build-pipeline plugin modified the publishers/ tag of the downstream project during the first deploy build, but with the second the publisher tag is left unmodified. In effect, the downstream project deployed the same application twice. 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.
[JIRA] [build-pipeline] (JENKINS-18162) Parameterized downstream project is missing upstream-set parameters when used by mutliple upstream projects
Benny Bottema edited a comment on JENKINS-18162 Parameterized downstream project is missing upstream-set parameters when used by mutliple upstream projects In an older Jenkins version (1.486, with build-pipeline 1.3.3) I looked up the /api/json for two deploy builds of the downstream project and noticed that the parameters are the same despite being triggered by different upstream builds in two separate pipelines. I also noticed the build-pipeline plugin modified the publishers/ tag of the downstream project during the first deploy build, but with the second the publisher tag is left unmodified. In effect, the downstream project deployed the same application twice. 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.
[JIRA] [build-pipeline] (JENKINS-18162) Parameterized downstream project is missing upstream-set parameters when used by mutliple upstream projects
Benny Bottema commented on JENKINS-18162 Parameterized downstream project is missing upstream-set parameters when used by mutliple upstream projects sooo... any chance we can solve this situation soon? 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.
[JIRA] [build-pipeline] (JENKINS-18162) Parameterized downstream project is missing upstream-set parameters when used by mutliple upstream projects
Ole Christian Langfjæran commented on JENKINS-18162 Parameterized downstream project is missing upstream-set parameters when used by mutliple upstream projects 1.3.4-SNAPSHOT is indeed bugged with the run button, the retry being the most importent one I think. https://issues.jenkins-ci.org/browse/JENKINS-11105. But passing parameters seems to work for me, unless i do a retry. Using 1.3.4-SNAPSHOT a new "Manual build other projects" is available. Can't remember the exact name as I'm on sickleave for a month from the project. But for the build that is manually triggered, the "triggering" project has to transfer the parameters to the build a second time. As an example if your manual build is a parameterized build with the parameter VERSION, you have to repeat it like so: VERSION=$VERSION Even if the first triggered build had the parameter with exact same name. At least, that's what I've experienced. Hope it helps, and hope a 1.3.4 version could be tagged and uploaded soon. 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.
[JIRA] [build-pipeline] (JENKINS-18162) Parameterized downstream project is missing upstream-set parameters when used by mutliple upstream projects
Ole Christian Langfjæran commented on JENKINS-18162 Parameterized downstream project is missing upstream-set parameters when used by mutliple upstream projects 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. 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.
[JIRA] [build-pipeline] (JENKINS-18162) Parameterized downstream project is missing upstream-set parameters when used by mutliple upstream projects
Benny Bottema edited a comment on JENKINS-18162 Parameterized downstream project is missing upstream-set parameters when used by mutliple upstream projects I have tried it, but considering I'm working on a production server with 30 projects (plus the 120 duplicates), I was hesitant to commit more time investigating, considering the Run button is bugged with the 1.3.4-SNAPSHOT. Don't know if it fixes it, but it's unusable just the same. This is a rather big issue for us. 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.
[JIRA] [build-pipeline] (JENKINS-18162) Parameterized downstream project is missing upstream-set parameters when used by mutliple upstream projects
Benny Bottema commented on JENKINS-18162 Parameterized downstream project is missing upstream-set parameters when used by mutliple upstream projects I have tried it, but considering I'm working on a production server with 30 projects, I was hesitant to commit more time investigating, considering the Run button is bugged with the 1.3.4-SNAPSHOT. Don't know if it fixes it, but it's unusable just the same. This is a rather big issue for us. 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.
[JIRA] [build-pipeline] (JENKINS-18162) Parameterized downstream project is missing upstream-set parameters when used by mutliple upstream projects
Benny Bottema created JENKINS-18162 Parameterized downstream project is missing upstream-set parameters when used by mutliple upstream projects Issue Type: 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 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.