[JIRA] (JENKINS-36544) Allow setting environment variables for dynamic ec2 slaves

[alexandre.bury@gmail.com (JIRA)]

Alexandre Bury created an issue

Jenkins / JENKINS-36544 Allow setting environment variables for dynamic ec2 slaves Issue Type: New Feature Assignee: Francis Upton Components: ec2-plugin Created: 2016/Jul/08 5:54 PM Priority: Minor Reporter: Alexandre Bury The ec2 plugin can dynamically create EC2 slaves with the given configuration. However, this configuration does not allow to specify environment variables to be used by the newly created nodes. I could update each created node one by one, but it seems inefficient considering more could be created when the load requires it. Adding an option in the ec2 plugin configuration with a list of environment variable for each slave configuration would be very useful. Add Comment

This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)

[ryan.wallner@clusterhq.com (JIRA)]

Ryan Wallner commented on JENKINS-36544

Re: Allow setting environment variables for dynamic ec2 slaves +1

Add Comment

[kyle@lodge.glasgownet.com (JIRA)]

Kyle Gordon commented on JENKINS-36544

Re: Allow setting environment variables for dynamic ec2 slaves

This would be a very useful feature to have, as we use custom AMIs for cross compilation that all rely on having a few environment variables set. Things like chroots, java_home, etc are all impossible just now.

Add Comment

[tlynchpin@gmail.com (JIRA)]

Tim Lynch commented on JENKINS-36544

Re: Allow setting environment variables for dynamic ec2 slaves

Global envvars are unable to have different values depending on the node, for example some nodes FOO=foo and others FOO=bar.   Can 'init script' be used to set envvars?

Add Comment

This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

[michelzanini@gmail.com (JIRA)]

Michel Zanini commented on JENKINS-36544

Re: Allow setting environment variables for dynamic ec2 slaves

This would be a good addition to the plugin. I use the same AMI ID, but I create different nodes with different labels, to be able to set different box sizes for different jobs matching those labels. For example, the same AMI ID is used, to create two t3.medium with "java" label to build Java apps, and two t3.small to build node apps with "node" label. I would like to be able to set different environment variables for them, but they are the same AMI, which makes this hard. If we could set different Node environment variables, already supported by Jenkins, but not supported by this plugin that would solve this issue nicely.

Add Comment

[marco.andries@itextpdf.com (JIRA)]

Marco Andries commented on JENKINS-36544

Re: Allow setting environment variables for dynamic ec2 slaves

We would also benefit greatly by this. We're blocked and asked the following question to reach a work around: https://stackoverflow.com/questions/58006452/issue-setting-jenkins-environment-variables-on-ec2-fleet

Add Comment

This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)

[jhansche@meetme.com (JIRA)]

Joe Hansche commented on JENKINS-36544

Re: Allow setting environment variables for dynamic ec2 slaves

It appears that this was implemented in https://github.com/jenkinsci/ec2-plugin/pull/382 However, I don't see a way to edit the properties in the AMI template, even though the config.jelly entry is supposed to be there. Am I missing something?

Add Comment

[jhansche@meetme.com (JIRA)]

Joe Hansche updated an issue

Jenkins / JENKINS-36544

Allow setting environment variables for dynamic ec2 slaves

Change By: Joe Hansche Attachment: Screen Shot 2020-03-09 at 11.29.38 AM.png

Add Comment

This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)

[jhansche@meetme.com (JIRA)]

Joe Hansche started work on JENKINS-36544

Change By: Joe Hansche Status: Open In Progress

Add Comment

[jhansche@meetme.com (JIRA)]

Joe Hansche updated JENKINS-36544

Jenkins / JENKINS-36544 Allow setting environment variables for dynamic ec2 slaves

Change By: Joe Hansche Status: In Progress Review

Add Comment

[jhansche@meetme.com (JIRA)]

Joe Hansche assigned an issue to Joe Hansche

Jenkins / JENKINS-36544 Allow setting environment variables for dynamic ec2 slaves

Change By: Joe Hansche Assignee: Francis Upton Joe Hansche

Add Comment

[jhansche@meetme.com (JIRA)]

Joe Hansche commented on JENKINS-36544

Re: Allow setting environment variables for dynamic ec2 slaves Turns out the original PR did resolve this, but only for Jenkins versions up to and including v2.204. As of 2.205, the Configure Clouds block moved to a new page, and that broke the Node Properties block. New PR has been opened to address this, which should now work on versions before and after 2.205: https://github.com/jenkinsci/ec2-plugin/pull/440

Add Comment