Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

EC2 Fleet Plugin With Label Restriction Does Not Scale When Pipeline Uses Label Conditions #361

Open
kzettlmeier opened this issue Apr 7, 2023 · 2 comments

Comments

@kzettlmeier
Copy link

Issue Details

Describe the bug
EC2 Fleet Plugin will not auto scale on node label expressions.

To Reproduce

  1. Create a new Jenkins job that uses node label linux-docker-fleet || windows-docker-fleet
  2. Create a new EC2 Fleet Cloud that should restrict to label linux-docker-fleet
  3. Create a new EC2 Fleet Cloud that should restrict to label windows-docker-fleet

Environment Details

Plugin Version?
2.5.2

Jenkins Version?
2.319.1

Label based fleet?
Yes

Linux or Windows?
Both

When Jenkins scans for if it needs to boot any new EC2 instances you will see the following log message:

label [linux-docker-fleet||windows-docker-fleet]: cloud AWS-Linux-Docker-Fleet can not provision for this label, continuing...
label [linux-docker-fleet||windows-docker-fleet]: cloud AWS-Windows-Docker-Fleet can not provision for this label, continuing...
@kzettlmeier kzettlmeier added the bug label Apr 7, 2023
@vineeth-bandi vineeth-bandi added stale Issues / PRs with no activity and removed stale Issues / PRs with no activity labels Aug 8, 2023
@vineeth-bandi
Copy link
Collaborator

@kzettlmeier
I was not able to reproduce this bug with Plugin version 2.5.2 and Jenkins version 2.319.2. Can you share screenshots of your Fleet Cloud configurations as well as Job configuration?

@ajax-koval-i
Copy link

@kzettlmeier hi have the same issue
did you fix that ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants