[rayci] Upload pipeline in batches when job count exceeds Buildkite limit#483
Merged
andrew-anyscale merged 1 commit intomainfrom Apr 8, 2026
Merged
Conversation
Contributor
Author
|
Reviews in this chain: |
Contributor
Author
Contributor
There was a problem hiding this comment.
Code Review
This pull request implements pipeline batching for Buildkite uploads to handle job limits. It adds functionality to calculate total jobs (including parallelism) and split pipelines into batches, ensuring the 'Notify' configuration is preserved in the first batch. Comprehensive tests were added to verify batching behavior. The reviewer suggested simplifying the implementation in main.go by always using the batching logic to avoid code duplication between the single-batch and multi-batch cases.
db2a0e7 to
b5817af
Compare
…imit Buildkite rejects pipeline uploads with more than 500 jobs > buildkite-agent: fatal: Failed to upload and process pipeline: Pipeline upload rejected: The number of jobs in this upload exceeds your organization limit of 500. Please break the upload into batches below this limit, or contact support to discuss an increase When the pipeline exceeds this limit (counting parallelism-expanded jobs), split it into batches by group and upload each batch separately. If any single group exceeds 500 jobs, error with a message to split the group. Topic: upload-batches Signed-off-by: andrew <andrew@anyscale.com>
b5817af to
89784b7
Compare
aslonnie
approved these changes
Apr 8, 2026
aslonnie
pushed a commit
to ray-project/ray
that referenced
this pull request
Apr 17, 2026
…ob limit (#62736) Buildkite rejects pipeline uploads above an organization-level job limit (500 at time of writing) with "Pipeline upload rejected: The number of jobs in this upload exceeds your organization limit of 500." The release pipeline's release_tests.json has grown past that; the previous "step dependencies not found" failure had been masking it. custom_image_build_and_test_init now splits the computed steps into batches of at most --max-jobs-per-upload jobs (default 450 for headroom) and writes each batch to .buildkite/release/release_tests_<i>.json. Groups are atomic — a single group that exceeds the limit raises, matching the approach taken in rayci (ray-project/rayci#483, #484). custom-image-build-and-test-init.sh iterates the chunks and uploads each in order so dependencies between steps in different chunks still resolve. Signed-off-by: andrew <andrew@anyscale.com>
HLDKNotFound
pushed a commit
to chichic21039/ray
that referenced
this pull request
Apr 22, 2026
…ob limit (ray-project#62736) Buildkite rejects pipeline uploads above an organization-level job limit (500 at time of writing) with "Pipeline upload rejected: The number of jobs in this upload exceeds your organization limit of 500." The release pipeline's release_tests.json has grown past that; the previous "step dependencies not found" failure had been masking it. custom_image_build_and_test_init now splits the computed steps into batches of at most --max-jobs-per-upload jobs (default 450 for headroom) and writes each batch to .buildkite/release/release_tests_<i>.json. Groups are atomic — a single group that exceeds the limit raises, matching the approach taken in rayci (ray-project/rayci#483, ray-project#484). custom-image-build-and-test-init.sh iterates the chunks and uploads each in order so dependencies between steps in different chunks still resolve. Signed-off-by: andrew <andrew@anyscale.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Buildkite rejects pipeline uploads with more than 500 jobs
When the pipeline exceeds this limit (counting parallelism-expanded jobs), split it into batches by group and upload each batch separately. If any single group exceeds 500 jobs, error with a message to split the group.
Topic: upload-batches
Signed-off-by: andrew andrew@anyscale.com