Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-19058

ec2-plugin cannot add specified instance tags on launched spot instances

    XMLWordPrintable

Details

    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

          Did you test the last version ? the Tag should be there for all type of the nodes

          thoulen FABRIZIO MANFREDI added a comment - Did you test the last version ? the Tag should be there for all type of the nodes
          sw97272 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.

          sw97272 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.

          I still don't have tags on spot instances in plugin version 1.39, Jenkins 2.136

          mykola Mykola Marzhan added a comment - I still don't have tags on spot instances in plugin version 1.39, Jenkins 2.136

          I think this is still an issue in version 1.38 of the ec2-plugin. Did this actually get released?

          dinesh_dh 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?
          aji9861 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.

          aji9861 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.

          People

            aji9861 Adam Irr
            henrysher Henry Huang
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: