Ci add gh actions #2091
Merged
Ci add gh actions #2091
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
ericoporto
force-pushed
the
ci-add-gh-actions
branch
from
a002251 to
6fe7919
Compare
|
I won't have time to work in CI stuff until September so it's better to run the less resources as possible. |
|
What are these skipped tasks for, are they used in preparing a Editor package (like a Linux build target), or no? |
This was referenced Aug 27, 2023
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 mostly disables CI for macOS and linux CMake in Cirrus CI, and instead expect those to happen in GitHub Actions - contributing to the goal of #2076
I think I would like to have GitHub Actions checking on a per commit basis and use Cirrus CI like before a PR merge (maybe triggering manually?), for releases, and maybe through a cron job that checks difference and builds nightly for master and ags4.
I won't do this in this PR though. I am leaving this as draft for a moment to think about this a bit more.
Ah, once all the recent CI stuff is merged in ags4 I probably need to also make the CMake build tests for the new compiler too.
port to 3.6.0 branch in #2115.