It behaves like the internal APIs do, not enforcing anything on parameters
being passed to builds -- which means defined parameters may not be set, and
undefined parameters may be set.
Which is probably the wrong approach for a user-facing script DSL.
On 11.09.2015, at 06:13, Michael Neale wro
Eric, this sounds like a bug, not a feature missing (or are they the same
thing ? ;), worth opening a ticket for?
On Thursday, September 10, 2015 at 10:12:43 PM UTC+10, Eric Engel wrote:
>
> Hi,
>
>
>
> I have this scenario:
>
>
>
> Job X with default Parameters A=1, B=2 and C=3. Workflow Jo
Hi,
I have this scenario:
Job X with default Parameters A=1, B=2 and C=3. Workflow Job Y calls Job X with
a build step:
>build job: 'X', propagate: false, parameters: [new
>hudson.model.StringParameterValue('A', '2'), new
>hudson.model.StringParameterValue('B', '3')]
What happens: Job X is c
