![]() |
|
|
|
|
Issue Type:
|
![Bug]() Bug
|
|
Assignee:
|
Francis Upton
|
|
Components:
|
ec2 |
|
Created:
|
29/May/14 7:10 PM
|
|
Description:
|
I just recently came across an old job of mine. It is not specified to run on any label, but ALL of my instances are reserved to run jobs that are explicitly tied to them. So when this job was accidentally started, it got stuck in the queue.
The EC2 plugin then proceeded to continuously spin up instances of the first AMI that I have in my configuration.
It's unacceptably bad ![]()
|
|
Environment:
|
CentOS6.4
Jenkins 1.565-1.1
EC2 Plugin 1.21
Matrix Build Plugin 1.2
|
|
Project:
|
Jenkins
|
|
Priority:
|
![Major]() Major
|
|
Reporter:
|
Kevin R.
|
|
|
|
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
|
--
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
[email protected].
For more options, visit
https://groups.google.com/d/optout.
