I defined it in the wrong place it looks like
This project is parameterized
Boolean Parameter
Then the parameter was passed to the downstream build
tirsdag 7. juni 2016 13.11.05 UTC+2 skrev Sverre Moe følgende:
>
> I tried that
> In the downstream job configuration:
> Prepare an environment for
I tried that
In the downstream job configuration:
Prepare an environment for the run -> Properties Content
-> UPSTREAM_TRIGGERED=false
Did not work.
tirsdag 7. juni 2016 12.57.21 UTC+2 skrev Antonio Muñiz følgende:
>
> On Tue, Jun 7, 2016 at 12:52 PM, Sverre Moe > wrote:
On Tue, Jun 7, 2016 at 12:52 PM, Sverre Moe wrote:
> How/where do i define the parameter?
The parameter must be defined in the downstream job (as any other
parameterized job).
--
Antonio Muñiz
Software Engineer
CloudBees, Inc.
--
You received this message because you
Using Jenkins 2.8.
How/where do i define the parameter?
1) For regular build jobs
Tried: Prepare an environment for the run -> Properties Content
-> UPSTREAM_TRIGGERED=false
Did not work. The value if always false, even if ProjectA sends the value
with true.
2) For pipeline jobs
Tried:
If you are using Jenkins 1.651.2 (or 2.3+) you are hitting the
SECURITY-170 fix: undeclared parameters are ignored (and not injected
as env vars).
You have to define the parameter (`UPSTREAM_TRIGGERED`) in the downstream build.
On Tue, Jun 7, 2016 at 9:39 AM, Sverre Moe
I am trying to pass a parameter to a scheduled build, but the build does
not get the parameter.
When ProjectA schedule a build of ProjectB it should pass along a parameter
I called UPSTREAM_TRIGGERED.
When ProjectB starts building there are no parameters passed in from
ProjectA.
I have the