CI: Reduce container and machine usage #2079
Merged
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
This was referenced Aug 7, 2023
Merged
ericoporto
force-pushed
the
ci-reduce-usage-a-bit
branch
from
636be8b to
4997df8
Compare
- make all macOS builds in a single machine - CMake Linux task builds Debug and Release - In CMake Linux task, pass j2 for minimal parallelism - Windows Engine and Editor tasks builds Debug and Release in the same task - Make sure a test runs right after one build, so we can fail earlier - for Linux make task (which doesn't make into release), drop the i386 build - we don't run tests in it - for the engine and tests, use VS builds with multiprocessor compilation
4 tasks
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 in-line with #2076, with the idea of reducing a bit the usage of Cirrus CI, the idea is we can possibly still stay under it's set limit of compute credits by doing few changes - I know these list above looks like a lot, but the general of the tasks done is the same and it produces the same binaries using the same containers.
This is safe to merge. I can prepare a proper version for merging in ags4 branch too - because of the 2nd compiler there are slight differences there.
port to 3.6.0 branch in #2115.