-
Notifications
You must be signed in to change notification settings - Fork 806
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Build: migrate from Travis to GH Actions #17902
Conversation
Scheduled Jetpack release: December 1, 2020. Thank you for the great PR description! When this PR is ready for review, please apply the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍 A few suggestions.
export PLUGIN_SLUG=$(basename $(pwd)) | ||
export PATH="$HOME/.config/composer/vendor/bin:$HOME/.composer/vendor/bin:$PATH" | ||
./tests/setup-travis.sh | ||
./tests/run-travis.sh |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's up to you, but I'd recommend moving all the stuff from setup-travis.sh and run-travis.sh in here into this file, or into .github/actions/ that are then called from here.
run-travis.sh, in particular, seems kind of spaghetti-ish and seems like it would be more clear split up into steps.
If you don't want to, that's fine with me but I may well do it in a followup 😉
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yeah, totally! I'll look at what can be done
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I guess I'm going to refactor it in a follow-up PR.
Co-authored-by: Brad Jorsch <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This seems to test well. Let's give it a try!
I would agree that it would be nice to consolidate everything in the .github
directory later on, it would be nice to clean things up.
Changes proposed in this Pull Request:
Jetpack product discussion
p9dueE-2bk-p2
Does this pull request change what data or activity we track or use?
n/a
Testing instructions:
Proposed changelog entry for your changes: