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

[michael.saw...@veeva.com (JIRA)]

Title: Message Title

Michael Sawyer commented on JENKINS-37381   Re: Two builds triggered when building on new ec2 slave 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. Add Comment   This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.