[JIRA] (JENKINS-54919) Newly defined parameters aren't available in Declarative agent configuration on first build
Title: Message Title Andrew Bayer updated an issue Jenkins / JENKINS-54919 Newly defined parameters aren't available in Declarative agent configuration on first build Change By: Andrew Bayer Sprint: Declarative backlog Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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/d/optout.
[JIRA] (JENKINS-54919) Newly defined parameters aren't available in Declarative agent configuration on first build
Title: Message Title Andrew Bayer updated JENKINS-54919 Jenkins / JENKINS-54919 Newly defined parameters aren't available in Declarative agent configuration on first build Change By: Andrew Bayer Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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/d/optout.
[JIRA] (JENKINS-54919) Newly defined parameters aren't available in Declarative agent configuration on first build
Title: Message Title Andrew Bayer commented on JENKINS-54919 Re: Newly defined parameters aren't available in Declarative agent configuration on first build PR up at https://github.com/jenkinsci/pipeline-model-definition-plugin/pull/301 - let's see if it doesn't regress anything else... Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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/d/optout.
[JIRA] (JENKINS-54919) Newly defined parameters aren't available in Declarative agent configuration on first build
Title: Message Title Andrew Bayer started work on JENKINS-54919 Change By: Andrew Bayer Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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/d/optout.
[JIRA] (JENKINS-54919) Newly defined parameters aren't available in Declarative agent configuration on first build
Title: Message Title
Andrew Bayer created an issue
Jenkins / JENKINS-54919
Newly defined parameters aren't available in Declarative agent configuration on first build
Issue Type:
Bug
Assignee:
Andrew Bayer
Components:
pipeline-model-definition-plugin
Created:
2018-11-28 13:53
Priority:
Major
Reporter:
Andrew Bayer
This is similar to both JENKINS-40574 and JENKINS-43911 (well, how JENKINS-43911 would behave from 1.2 onward - previously it was just that environment was evaluated after agent during execution) - parameters is evaluated at the beginning of the Declarative runtime, but agent is populated before that, at the very start of execution. So if params.FOO already exists when the build starts, then agent { label params.FOO }}} will work fine, but if it's a new parameter (like, say, on first build of a branch), {{params.FOO's value there will end up as null. A workaround for now is to do label "${params.FOO ?: 'whatever-the-default-value-should-be'}", but I'll work on a better solution.
Add Comment
