-
Type:
Bug
-
Resolution: Not A Defect
-
Priority:
Minor
-
Component/s: ec2-plugin
-
None
Hi,Â
We currently have 25 Windows nodes that are spawned by the EC2 plugin and when they are idle they are stopped (not terminated).Â
We noticed recently that one of our nodes had an issue and the EC2 plugin ran the same pipeline on it five times. Although that is not the fault of the EC2 plugin!
Â
We were wondering what the scheduling mechanism is i.e. how does the plugin / Jenkins Controller determine what node to run a given pipeline Â