Skip to content
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

Merged
merged 1 commit into from
Apr 1, 2022
Merged

Migrate CI to GitHub Actions #16

merged 1 commit into from
Apr 1, 2022

Conversation

tsibley
Copy link
Member

@tsibley tsibley commented Apr 1, 2022

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).

@tsibley tsibley requested review from j23414 and victorlin April 1, 2022 20:26
@tsibley
Copy link
Member Author

tsibley commented Apr 1, 2022

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.

@tsibley tsibley requested a review from a team April 1, 2022 20:30
Copy link
Contributor

@j23414 j23414 left a 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!

README.md Show resolved Hide resolved
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)>.
tsibley added a commit to nextstrain/.github that referenced this pull request Apr 1, 2022
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
@tsibley tsibley merged commit edf0d73 into master Apr 1, 2022
tsibley added a commit to nextstrain/.github that referenced this pull request Apr 1, 2022
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
tsibley added a commit to nextstrain/.github that referenced this pull request Apr 1, 2022
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
tsibley added a commit to nextstrain/.github that referenced this pull request Apr 1, 2022
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
tsibley added a commit to nextstrain/measles that referenced this pull request Apr 1, 2022
@tsibley tsibley deleted the trs/ci branch April 1, 2022 23:54
tsibley pushed a commit to nextstrain/avian-flu that referenced this pull request Apr 4, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants