Work around stale results in GH jobs API - #2720
Merged
Merged
Conversation
Starting yesterday, the GH jobs API started returning stale commit information (seemingly random). This caused the code which detects the plugins to build (from the last successful CI run) to select a large number of plugins to build and publish which were unchanged. This adds unnecessary load on the system and creates new plugin revisions in the BSR unnecessarily. Update the CI workflow to use the new `queue: max` concurrency setting to ensure we build every commit pushed to main. With this setting in place, we only need to look at what changed since the prior commit (assuming all commits will build). If we ever need to force a rebuild of a plugin, that is possible with a manual run of the CI workflow and specifying the PLUGINS input.
oliversun9
approved these changes
Sep 3, 2026
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
2 participants
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.
Starting yesterday, the GH jobs API started returning stale commit information (seemingly random). This caused the code which detects the plugins to build (from the last successful CI run) to select a large number of plugins to build and publish which were unchanged.
This adds unnecessary load on the system and creates new plugin revisions in the BSR unnecessarily.
Update the CI workflow to use the new
queue: maxconcurrency setting to ensure we build every commit pushed to main. With this setting in place, we only need to look at what changed since the prior commit (assuming all commits will build). If we ever need to force a rebuild of a plugin, that is possible with a manual run of the CI workflow and specifying the PLUGINS input.