-
Notifications
You must be signed in to change notification settings - Fork 12
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
migrating from Travis to GitHub Actions #236
Comments
Not that familiar with GitHub actions, does it do about the same thing as Travis? After a quick glance at PheKnowLator it does look powerful |
It provides a nice free alternative to Travis since it's now moved to being a paid service. I have tried to configure it to shadow @LucaCappelletti94's original Travis configuration, so you shouldn't notice any feature loss. I am really loving it for how easy it is to build in other functionality (e.g. deploying containers and integration with cloud-based storage services) and it seems to run faster than Travis did (at least for my repos). |
Good idea Tiffany - I did the conversion from Travis to GH actions to run
unit tests and linters for KG-COVID-19 and NEAT, I might be able to help a
bit too.
Not sure if I’m admin on Embiggen, but if not yeah we’d need Peter or
someone else with admin to help
On Tue, Dec 29, 2020 at 08:59 Peter Robinson ***@***.***> wrote:
Not that familiar with GitHub actions, does it do about the same thing as
Travis? After a quick glance at PheKnowLator it does look powerful
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#236 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AABEWJ4QFRZTSWORCDMZUEDSXIDFZANCNFSM4VNL3LTA>
.
--
Justin Reese, Ph.D.
Berkeley Bioinformatics Open-source Projects
Lawrence Berkeley National Laboratory
phone (415) 909-9418 | (510) 486-5078
|
Does anyone have expertise in GitHub action? I would love to see them used for the package but I am absolutely ignorant of them as of now. |
@justaddcoffee has some experience and I have done this in some other projects. Poorly documented. We could hack on it. |
I'm not terrible at github actions - maybe we can hack on this tomorrow @LucaCappelletti94 @pnrobinson |
If it is helpful, I converted a very similar set-up from Tavis to GitHub Actions. You might be able to start from this. https://github.com/callahantiff/PheKnowLator/blob/master/.github/workflows/build-qa.yml |
Do we want to migrate from Travis to GitHub Actions? If so, I am happy to do the work. I converted Luca's pipeline to run with all of the same coverage metrics for my repositories and am happy to do the same for this repo (examples here and here).
Given the permissions needed to make transformation, I'd likely need to do some of the work with @pnrobinson, but now that I have done the conversion on a few repos it should be pretty painless!
The text was updated successfully, but these errors were encountered: