Set up GitHub Actions CI#1623
Merged
Merged
Conversation
nguyenhuy
force-pushed
the
HN-Actions
branch
3 times, most recently
from
August 17, 2019 14:41
7b54e5f to
7c02019
Compare
- examples-pt3 builds the same examples as examples-pt1 instead of building the remaining projects. So I fixed it.
- Add another mode (examples-pt4) to distribute the load with existing steps.
- Build extra examples (examples-extra-pt{1, 2, 3}) which weren't built before.
- Each examples-pt and examples-extra-pt builds 5 projects except examples-pt4 and examples-extra-pt3 which build 6.
nguyenhuy
force-pushed
the
HN-Actions
branch
5 times, most recently
from
August 17, 2019 23:17
7220daf to
d67280d
Compare
nguyenhuy
force-pushed
the
HN-Actions
branch
6 times, most recently
from
August 18, 2019 00:00
df934aa to
b86d2cb
Compare
appleguy
self-requested a review
August 18, 2019 21:26
appleguy
approved these changes
Aug 18, 2019
appleguy
left a comment
appleguy
left a comment
Member
There was a problem hiding this comment.
Thanks a lot for your work on this, Huy! Definitely a big positive step for the Texture community!
Member
Author
|
I’m super excited about the new CI! Thanks everyone for your reviews. Let’s get it in! I’ll follow up to deprecate BuildKite CI. |
matthewd1234
pushed a commit
to matthewd1234/Texture
that referenced
this pull request
Aug 25, 2019
GitHub Actions now supports CI and it's free for open source projects!
Our current CI runs on a single machine and needs 1h 20m for each build. GitHub CI often finishes everything in less than 10m!
The setup is straight-forward. The only missing feature is the ability to exclude certain files so that if a commit only contains those files, the CI won't test it at all (see exclude-from-build.json). Given that GitHub CI is fast and is not a serial queue, I wouldn't mind testing such commit as well.
* Fix and optimize steps that build example projects
- examples-pt3 builds the same examples as examples-pt1 instead of building the remaining projects. So I fixed it.
- Add another mode (examples-pt4) to distribute the load with existing steps.
- Build extra examples (examples-extra-pt{1, 2, 3}) which weren't built before.
- Each examples-pt and examples-extra-pt builds 5 projects except examples-pt4 and examples-extra-pt3 which build 6.
* Use HTTPS URL for Weaver in Podfile of examples/ASDKgram
* Don't build extra examples for now
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
4 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.
GitHub Actions now supports CI and it's free for open source projects!
Our current CI (BuildKite) runs on a single machine and needs 1h 20m for each build. GitHub CI often finishes everything in less than 10m!
The setup is straight-forward. The only missing feature is the ability to exclude certain files so that if a commit only contains those files, the CI won't test it at all (see exclude-from-build.json). Given that GitHub CI is fast and is not a serial queue, I wouldn't mind testing such commit as well.
Follow-up tasks if we land this:
master.