ci: split build out of test workflow#2197
Open
thompson-tomo wants to merge 32 commits intoopen-telemetry:mainfrom
Open
ci: split build out of test workflow#2197thompson-tomo wants to merge 32 commits intoopen-telemetry:mainfrom
thompson-tomo wants to merge 32 commits intoopen-telemetry:mainfrom
Conversation
88a5bfa to
790e2cc
Compare
790e2cc to
213b66c
Compare
arielvalentin
requested changes
Apr 18, 2026
Co-authored-by: Ariel Valentin <arielvalentin@users.noreply.github.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.
This introduces a ruby build Workflow which is responsible for building documentation and the gem. Previously this was being done via the testing Workflow only on 1 runtime.
By splitting it out in the future we can remove the build step from the testing workflows which will facilitate further optimisation in particular having all runtime testing behaving the same and more significantly using a matrix property for runtimes.
It is important to note that we have managed to restrict which gems are built to just be those that have changed hence improves ci performance.
This pattern of restricting will be replicated to the test workflows in the future hence brings benefit across the board.
In cases such as merge queue all gems will be built.
An example of what happens if no gems are identified can be seen at thompson-tomo#201