[JIRA] (JENKINS-51581) Add option to override tool config for slave nodes created by EC2 plugin

10 views
Skip to first unread message

dominik.heimstaedt@gmail.com (JIRA)

unread,
May 29, 2018, 7:56:02 AM5/29/18
to jenkinsc...@googlegroups.com
Dominik Heimstädt updated an issue
 
Jenkins / Improvement JENKINS-51581
Add option to override tool config for slave nodes created by EC2 plugin
Change By: Dominik Heimstädt
Summary: Add option to override tool config for J slave nodes created by EC2 plugin
Add Comment Add Comment
 
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
Atlassian logo

cimpoiesgeorge@gmail.com (JIRA)

unread,
Oct 10, 2019, 6:31:03 AM10/10/19
to jenkinsc...@googlegroups.com
George Cimpoies updated an issue
Change By: George Cimpoies
Priority: Minor Major
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
Atlassian logo

cimpoiesgeorge@gmail.com (JIRA)

unread,
Oct 10, 2019, 6:34:01 AM10/10/19
to jenkinsc...@googlegroups.com
George Cimpoies commented on Improvement JENKINS-51581
 
Re: Add option to override tool config for slave nodes created by EC2 plugin

This is a show-stopper for us as we want to rely solely on aws for our build agents, but we can't define global tool locations since we have many different jobs and configurations on Jenkins.

With hardware nodes we use swarm plugin + a script like this:

"$($env:JDK8_PATH)\bin\java.exe" `
    -cp "$($env:USERPROFILE)\slave.jar" `
    -jar "$($env:USERPROFILE)\swarm-client.jar" `
    -deleteExistingClients `
    -name "$($env:HOSTNAME)" `
    -disableClientsUniqueId `
    -fsroot "$($env:USERPROFILE)" `
    -description "$($env:JENKINS_NODE_DESCRIPTION)" `
    -master "$($env:JENKINS_MASTER)" `
    -executors "$($env:JENKINS_NUMBER_OF_EXECUTORS)" `
    -labels "$($env:JENKINS_NODE_LABELS)" `
    --toolLocation "jdk7=$($env:JDK7_PATH)" `
    --toolLocation "jdk8=$($env:JDK8_PATH)" `
    --toolLocation "jdk9=$($env:JDK9_PATH)" `
    --toolLocation "jdk10=$($env:JDK10_PATH)" `
    --toolLocation "jdk11=$($env:JDK11_PATH)" `

to add the tool locations on the node that's connecting to Jenkins.

cimpoiesgeorge@gmail.com (JIRA)

unread,
Oct 10, 2019, 6:35:06 AM10/10/19
to jenkinsc...@googlegroups.com
George Cimpoies updated an issue
Change By: George Cimpoies
Environment: Jenkins 2.107.3, Amazon EC2 Plugin 1. 39 46.1

cimpoiesgeorge@gmail.com (JIRA)

unread,
Oct 10, 2019, 6:35:06 AM10/10/19
to jenkinsc...@googlegroups.com

cimpoiesgeorge@gmail.com (JIRA)

unread,
Oct 10, 2019, 6:35:06 AM10/10/19
to jenkinsc...@googlegroups.com
George Cimpoies edited a comment on Improvement JENKINS-51581
This is a show-stopper for us as we want to rely solely on aws for our build agents, but we can't define global tool locations since we have many different jobs and configurations on Jenkins.

With hardware nodes we use swarm plugin + a script like this:
{code:java}

"$($env:JDK8_PATH)\bin\java.exe" `
    -cp "$($env:USERPROFILE)\slave.jar" `
    -jar "$($env:USERPROFILE)\swarm-client.jar" `
    -
deleteExistingClients `
    -name "$($env:HOSTNAME)" `
    -disableClientsUniqueId `
    -
fsroot "$($env:USERPROFILE)" `

    -description "$($env:JENKINS_NODE_DESCRIPTION)" `
    -master "$($env:JENKINS_MASTER)" `
    -executors "$($env:JENKINS_NUMBER_OF_EXECUTORS)" `
    -labels "$($env:JENKINS_NODE_LABELS)" `
    --toolLocation "jdk7=$($env:JDK7_PATH)" `
    --toolLocation "jdk8=$($env:JDK8_PATH)" `
    --toolLocation "jdk9=$($env:JDK9_PATH)" `
    --toolLocation "jdk10=$($env:JDK10_PATH)" `
    --toolLocation "jdk11=$($env:JDK11_PATH)" `
{code}

to add the tool locations on the node that's connecting to Jenkins.

cimpoiesgeorge@gmail.com (JIRA)

unread,
Oct 10, 2019, 10:51:02 AM10/10/19
to jenkinsc...@googlegroups.com

rsandell@cloudbees.com (JIRA)

unread,
Oct 15, 2019, 4:25:02 AM10/15/19
to jenkinsc...@googlegroups.com
rsandell updated an issue
 
Change By: rsandell
Labels: configuration slave tools triaged
Reply all
Reply to author
Forward
0 new messages