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

Travis CI free usage ends Dec 3; mozilla repos should switch to other CI platforms #1333

Closed
hwine opened this issue Dec 17, 2020 · 7 comments · Fixed by #1334
Closed

Travis CI free usage ends Dec 3; mozilla repos should switch to other CI platforms #1333

hwine opened this issue Dec 17, 2020 · 7 comments · Fixed by #1334

Comments

@hwine
Copy link

hwine commented Dec 17, 2020

We're opening this issue because your project has used Travis CI within the last 6 months. If you have already migrated off it, you can close and ignore this issue.

Travis CI is ending free builds on public repositories. travis-ci.com stopped providingthem in early November, and travis-ci.org will stop after December 31, 2020. To avoid disruptions to your workflows, you must migrate to another CI service.

For production use cases, we recommend switching to CircleCI. This service is already widely used within Mozilla. There is a guide to migrating from Travis CI to CircleCI available here.

For non production use cases, we recommend either CircleCI or Github Actions. There is a guide to migrating from Travis CI to Github Actions available here. Github Actions usage within Mozilla is new, and you will have to work with our github administrators to enable specific actions following this process.

If you have any questions, reach out in #github-admin:mozilla.org on matrix.

@leosdad
Copy link

leosdad commented Dec 17, 2020

I'm not sure what this means for Nunjucks users. Would you care to explain?

@fdintino
Copy link
Collaborator

It won't have anny effect on users, but I will have to migrate to a different CI option to continue to have tests run on pull requests and commits.

@ogonkov
Copy link
Contributor

ogonkov commented Dec 17, 2020

I think i can migrate repo to GH actions. I do that for my packages twice.

@ogonkov
Copy link
Contributor

ogonkov commented Dec 19, 2020

Appveyor seems to duplicate GitHub Actions, should it be replaced aswell?

@fdintino
Copy link
Collaborator

@hwine Would it be possible to add codecov/codecov-action@v1 to the list of allowed actions? It looks like only organization administrators have permissions to edit allowed actions.

@hwine
Copy link
Author

hwine commented Dec 31, 2020

The procedure for requesting additions is documented in wikimo.

@fdintino
Copy link
Collaborator

Thank you for pointing me to that. I've opened a bugzilla ticket for the request

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 a pull request may close this issue.

4 participants