Batch keyboard builds into groups of 16 per job#24
Merged
Conversation
Reduces job overhead by building multiple keyboards per CI job instead of spawning a separate job for each keyboard.
- Continue building remaining keyboards if one fails - Use if: always() on artifact upload step - Track failures and report at end of batch
- Downloads all firmware-batch-* artifacts - Merges into single 'firmware' artifact with all files - Deletes intermediate batch artifacts
- collect job outputs list of firmware filenames - upload-individual job uses matrix to upload each file separately - Each artifact named after the firmware file (without extension)
patcoll
changed the title
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
1 participant
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.
Summary
firmware-batch-N)Test plan