Skip to content

fix(azure-pipelines): exclude already-assigned jobs from queue length#7757

Merged
wozniakjan merged 1 commit into
kedacore:mainfrom
rickbrouwer:issue-7747
May 25, 2026
Merged

fix(azure-pipelines): exclude already-assigned jobs from queue length#7757
wozniakjan merged 1 commit into
kedacore:mainfrom
rickbrouwer:issue-7747

Conversation

@rickbrouwer

Copy link
Copy Markdown
Member

stripDeadJobs only filters jobs by Result, so jobs already picked up by an agent (with ReceiveTime set) keep counting towards the queue length. Each poll then spawns another agent until maxReplicaCount is hit, leaving dangling agents that do no work but consume parallel job slots.

Checklist

  • I have verified that my change is according to the deprecations & breaking changes policy
  • Tests have been added (if applicable)
  • Ensure make generate-scalers-schema has been run to update any outdated generated files
  • Changelog has been updated and is aligned with our changelog requirements, only when the change impacts end users
  • Commits are signed with Developer Certificate of Origin (DCO - learn more)

Fixes #7747

@rickbrouwer rickbrouwer requested a review from a team as a code owner May 21, 2026 20:26
@github-actions

Copy link
Copy Markdown

Thank you for your contribution! 🙏

Please understand that we will do our best to review your PR and give you feedback as soon as possible, but please bear with us if it takes a little longer as expected.

While you are waiting, make sure to:

  • Add an entry in our changelog in alphabetical order and link related issue
  • Update the documentation, if needed
  • Add unit & e2e tests for your changes
  • GitHub checks are passing
  • Is the DCO check failing? Here is how you can fix DCO issues

Once the initial tests are successful, a KEDA member will ensure that the e2e tests are run. Once the e2e tests have been successfully completed, the PR may be merged at a later date. Please be patient.

Learn more about our contribution guide.

@keda-automation keda-automation requested a review from a team May 21, 2026 20:26
@snyk-io

snyk-io Bot commented May 21, 2026

Copy link
Copy Markdown

Snyk checks have passed. No issues have been found so far.

Status Scan Engine Critical High Medium Low Total (0)
Open Source Security 0 0 0 0 0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

Comment thread pkg/scalers/azure_pipelines_scaler_test.go
Comment thread pkg/scalers/azure_pipelines_scaler_test.go
@rickbrouwer rickbrouwer added the required:keda-v2.20 This is absolutely mandatory to bring along label May 21, 2026
@rickbrouwer

rickbrouwer commented May 22, 2026

Copy link
Copy Markdown
Member Author

/run-e2e azure_pipelines
Update: You can check the progress here

@wozniakjan wozniakjan added the Awaiting/2nd-approval This PR needs one more approval review label May 22, 2026
@wozniakjan wozniakjan merged commit e6e6fe1 into kedacore:main May 25, 2026
25 checks passed
@rickbrouwer rickbrouwer deleted the issue-7747 branch May 25, 2026 10:46
shcherbak pushed a commit to shcherbak/keda that referenced this pull request Jun 3, 2026
@rickbrouwer rickbrouwer removed the Awaiting/2nd-approval This PR needs one more approval review label Jun 5, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

required:keda-v2.20 This is absolutely mandatory to bring along

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Azure Pipeline Scaler should check whether job has been picked up yet

2 participants