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

When a Jenkins job with no agent or wrong agent is executed, the EC2 fleet plugin is spinning up all the possible instances in all the clouds configured with different Agent Labels

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Cannot Reproduce
    • ec2-fleet-plugin
    • jenkins 2.176.2, EC2-fleet-jenkins-plugin 1.10.0

    Description

      If we have 4 EC2 spot fleet clouds configured to spin a maximum of 20 instances based on the agent label specified, if a jenkins job with no agent specified is executed, the build stays in the queue searching for agents and this is triggering all the 20 possible instances. Expected result would be to spin the instance only if the label assigned to the cloud is matched with the label specified in the Job

      Attachments

        Activity

          siva_baisani sivanarayana baisani created issue -
          siva_baisani sivanarayana baisani made changes -
          Field Original Value New Value
          Resolution Cannot Reproduce [ 5 ]
          Status Open [ 1 ] Closed [ 6 ]

          People

            schmutze Chad Schmutzer
            siva_baisani sivanarayana baisani
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: