[I-Build-Tests] Inline 'testAll' scripts #2516
Draft
Conversation
This file contains 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 is currently a draft since I have to test this locally first.
As a follow-up we could consider to inline the
runtests.sh/batscripts as well or at least to simplify them to what's still relevant nowadays.Keeping might be interesting for those that run I-builds locally, but on the long run I would like to simplify the set up to an extend so that we can provide a simple launch config to run the I-build locally for the current platform and with the current config in this repo. The compiled archives would then be either provided locally (if one wants to test changes) or be fetched from a matching I-build. But that's another story.