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

Two builds triggered when building on new ec2 slave

    • Icon: Bug Bug
    • Resolution: Cannot Reproduce
    • Icon: Major Major
    • ec2-plugin
    • None
    • Jenkins version 1.642.4
      ec2-plugin version 1.31

      When the ec2-plugin has to spin up the first machine for a cloud, two builds are triggered. This results in one build with the changes, and a second redundant build with the same commit, and no new changes listed.

          [JENKINS-37381] Two builds triggered when building on new ec2 slave

          Francis Upton added a comment -

          Can you provide the logs when this happens?

          Francis Upton added a comment - Can you provide the logs when this happens?

          After first build is triggered:

          Aug 16, 2016 6:46:23 AM hudson.plugins.ec2.EC2Cloud provision
          INFO: Attempting provision - finished, excess workload: 0
          Aug 16, 2016 6:46:23 AM hudson.slaves.NodeProvisioner$StandardStrategyImpl apply
          INFO: Started provisioning Slave1 (ami-00000001) from ec2-PrivateSubnet with 1 executors. Remaining excess workload: 0
          

          After this it provisions and connects to this slave, then a few minutes later:

          Aug 16, 2016 6:50:13 AM hudson.plugins.ec2.EC2Cloud provision
          INFO: Attempting provision - finished, excess workload: 0
          Aug 16, 2016 6:50:13 AM hudson.slaves.NodeProvisioner$StandardStrategyImpl apply
          INFO: Started provisioning Slave1 (ami-00000001) from ec2-PrivateSubnet with 1 executors. Remaining excess workload: -0.288
          

          This second build is built on the same commit id, with no new changes.

          Michael Sawyer added a comment - After first build is triggered: Aug 16, 2016 6:46:23 AM hudson.plugins.ec2.EC2Cloud provision INFO: Attempting provision - finished, excess workload: 0 Aug 16, 2016 6:46:23 AM hudson.slaves.NodeProvisioner$StandardStrategyImpl apply INFO: Started provisioning Slave1 (ami-00000001) from ec2-PrivateSubnet with 1 executors. Remaining excess workload: 0 After this it provisions and connects to this slave, then a few minutes later: Aug 16, 2016 6:50:13 AM hudson.plugins.ec2.EC2Cloud provision INFO: Attempting provision - finished, excess workload: 0 Aug 16, 2016 6:50:13 AM hudson.slaves.NodeProvisioner$StandardStrategyImpl apply INFO: Started provisioning Slave1 (ami-00000001) from ec2-PrivateSubnet with 1 executors. Remaining excess workload: -0.288 This second build is built on the same commit id, with no new changes.

          Cannot reproduce with last version.

          FABRIZIO MANFREDI added a comment - Cannot reproduce with last version.

            francisu Francis Upton
            michael_sawyer_veeva Michael Sawyer
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: