[JIRA] [build-pipeline-plugin] (JENKINS-18162) Parameterized downstream project is missing upstream-set parameters when used by mutliple upstream projects

0 views
Skip to first unread message

dylan.williams@wpengine.com (JIRA)

unread,
May 25, 2016, 3:27:01 PM5/25/16
to jenkinsc...@googlegroups.com
Dylan Williams commented on Bug JENKINS-18162
 
Re: Parameterized downstream project is missing upstream-set parameters when used by mutliple upstream projects

This functionality works with the latest release, unless your projects are inside of folders (cloudbees folder plugin).
Add Comment Add Comment
 
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
Atlassian logo

andy_dean@hotmail.co.uk (JIRA)

unread,
Jul 30, 2019, 6:53:02 AM7/30/19
to jenkinsc...@googlegroups.com

I'm getting this issue with up to date plugins and it is 2019... I have an upstream job calling a downstream one and it occasionally figures out what to do with parameters but other times it pretends like they don't exist and executes anyway.
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

andy_dean@hotmail.co.uk (JIRA)

unread,
Jul 30, 2019, 9:15:03 AM7/30/19
to jenkinsc...@googlegroups.com
Andrew Dean updated an issue
 
Jenkins / Bug JENKINS-18162
Change By: Andrew Dean
Comment:
I'm getting this issue with up to date plugins and it is 2019... I have an upstream job calling a downstream one and it occasionally figures out what to do with parameters but other times it pretends like they don't exist and executes anyway.
Reply all
Reply to author
Forward
0 new messages