Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
Jenkins 1.525, Amazon EC2 plugin v1.19-unreleased (last commit: #1e009adfa3)
Description
It is really urgent for me to choose the latest EC2 plugin (still not released) in testing. It seems that there are no latest commits since two months ago.
I have configured the tags for my new spot instance request, like:
Name: Name
Value: Henry
But after the spot instance launched, it seems no tags have been attached to this spot instance.
Could you please fix it before the official release?
Thanks
Henry
Attachments
Activity
simon Wall
added a comment - Is there any further development on this ticket? I am hopeful to be able to make use of the EC2 plugin's ability to manage worker nodes using spot instances, but we need to have tags passed to the instance.
simon Wall
added a comment - Is there any further development on this ticket? I am hopeful to be able to make use of the EC2 plugin's ability to manage worker nodes using spot instances, but we need to have tags passed to the instance. 
Mykola Marzhan
added a comment - I still don't have tags on spot instances in plugin version 1.39, Jenkins 2.136
Mykola Marzhan
added a comment - I still don't have tags on spot instances in plugin version 1.39, Jenkins 2.136 
Dinesh Dharmawardena
added a comment - I think this is still an issue in version 1.38 of the ec2-plugin. Did this actually get released?
Dinesh Dharmawardena
added a comment - I think this is still an issue in version 1.38 of the ec2-plugin. Did this actually get released? 
Adam Irr
added a comment - I was able to connect with the following command:
java -jar slave.jar -jnlpCredentials user:passsword -jnlpUrl http://ec2-xxx-xx-xxx-xxx.compute-1.amazonaws.com:8080/computer/XXXXXX-XXXXXXX/slave-agent.jnlp
This however requires you put the user password in the command parameters.
There should be a way to use your auth token instead of your password, but when I try I am getting a 401. Issues with connecting a slave using jnlp are not specific to this plugin/Spot instances. It uses the standard Jenkins jnlp information.
Adam Irr
added a comment - I was able to connect with the following command:
java -jar slave.jar -jnlpCredentials user:passsword -jnlpUrl http://ec2-xxx-xx-xxx-xxx.compute-1.amazonaws.com:8080/computer/XXXXXX-XXXXXXX/slave-agent.jnlp
This however requires you put the user password in the command parameters.
There should be a way to use your auth token instead of your password, but when I try I am getting a 401. Issues with connecting a slave using jnlp are not specific to this plugin/Spot instances. It uses the standard Jenkins jnlp information. 
Did you test the last version ? the Tag should be there for all type of the nodes