-
Notifications
You must be signed in to change notification settings - Fork 11
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
Migrate CI to GitHub Actions #16
Conversation
If this is acceptable to folks, then I would also plan to refactor it out into https://github.com/nextstrain/.github as a starter workflow + reusable workflow pair that we can then apply (and maintain) across the board to all/most of our pathogen repos. |
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 passed travis checks, and I like the migration to GH so looks good to me! Thanks!
We've been slowly moving everything off Travis CI in favor of centralizing on GitHub. More acutely motivated here by some Travis-specific errors, previously worked around by <#14>. Reverts back to a simple pip install instead of conda/mamba setup as much of it was unnecessary. See discussion in <nextstrain/measles#3 (comment)>.
The goal is to establish a common setup for CI for all or at least most of our pathogen build repos. Includes a reusable workflow¹ which can be called/invoked by our workflows in other repos and a "starter" workflow template² that performs such a call, for copying into the pathogen repo (either manually or via the web UI which supports these starter workflows). These are both basic for now but appropriate for our "simple" pathogen builds like zika and measles. We can add workflow parameters and conditionals as necessary in the future to support CI for more complex builds, like ncov. (It won't take much!) Related to <nextstrain/zika#16>. ¹ https://docs.github.com/en/actions/using-workflows/reusing-workflows ² https://docs.github.com/en/actions/using-workflows/creating-starter-workflows-for-your-organization
The goal is to establish a common setup for CI for all or at least most of our pathogen build repos. Includes a reusable workflow¹ which can be called/invoked by our workflows in other repos and a "starter" workflow template² that performs such a call, for copying into the pathogen repo (either manually or via the web UI which supports these starter workflows). These are both basic for now but appropriate for our "simple" pathogen builds like zika and measles. We can add workflow parameters and conditionals as necessary in the future to support CI for more complex builds, like ncov. (It won't take much!) Related to <nextstrain/zika#16>. ¹ https://docs.github.com/en/actions/using-workflows/reusing-workflows ² https://docs.github.com/en/actions/using-workflows/creating-starter-workflows-for-your-organization
The goal is to establish a common setup for CI for all or at least most of our pathogen build repos. Includes a reusable workflow¹ which can be called/invoked by our workflows in other repos and a "starter" workflow template² that performs such a call, for copying into the pathogen repo (either manually or via the web UI which supports these starter workflows). These are both basic for now but appropriate for our "simple" pathogen builds like zika and measles. We can add workflow parameters and conditionals as necessary in the future to support CI for more complex builds, like ncov. (It won't take much!) Related to <nextstrain/zika#16>. ¹ https://docs.github.com/en/actions/using-workflows/reusing-workflows ² https://docs.github.com/en/actions/using-workflows/creating-starter-workflows-for-your-organization
The goal is to establish a common setup for CI for all or at least most of our pathogen build repos. Includes a reusable workflow¹ which can be called/invoked by our workflows in other repos and a "starter" workflow template² that performs such a call, for copying into the pathogen repo (either manually or via the web UI which supports these starter workflows). These are both basic for now but appropriate for our "simple" pathogen builds like zika and measles. We can add workflow parameters and conditionals as necessary in the future to support CI for more complex builds, like ncov. (It won't take much!) Related to <nextstrain/zika#16>. ¹ https://docs.github.com/en/actions/using-workflows/reusing-workflows ² https://docs.github.com/en/actions/using-workflows/creating-starter-workflows-for-your-organization
We've been slowly moving everything off Travis CI in favor of
centralizing on GitHub. More acutely motivated here by some
Travis-specific errors, previously worked around by
#14.
Reverts back to a simple pip install instead of conda/mamba setup as
much of it was unnecessary. See discussion in
nextstrain/measles#3 (comment).