★ wanayoo — archive 1999 https://github.com/python-control/python-control/issues/446Nouvelle recherche | Portail wanayoo
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

Move from legacy Travis CI integration to a Github Actions based system #446

Open
bnavigator opened this issue Aug 4, 2020 · 5 comments
Open

Comments

@bnavigator
Copy link
Contributor

@bnavigator bnavigator commented Aug 4, 2020

@murrayrm
Copy link
Member

@murrayrm murrayrm commented Aug 5, 2020

I remember this was going to go away, but wasn't sure when. We need to set up a GitHub action instead. I'll try to do that in the next few days.

@bnavigator
Copy link
Contributor Author

@bnavigator bnavigator commented Aug 17, 2020

I agree that a move to Github actions will be necessary at some time.

Travis still reports the new run after the most recent merge. And the PR runs are still there just not reported on the PR pages.

@bnavigator
Copy link
Contributor Author

@bnavigator bnavigator commented Aug 18, 2020 •

The PR run checks came back. Not sure, why. Probably a refresh of Travis' API tokens and rate limits.

@bnavigator bnavigator changed the title Travis CI does not report runs on Github PRs Move from legacy Travis CI integration to a Github Actions based system Aug 18, 2020
@murrayrm
Copy link
Member

@murrayrm murrayrm commented Aug 18, 2020

You (@bnavigator) apparently put in some sort of request to set up the GitHub/Travis CI integration. I got an e-mail asking for approval of the permissions and I approved. So presumably that turned things back on (and hopefully didn't break anything!).

@bnavigator
Copy link
Contributor Author

@bnavigator bnavigator commented Aug 18, 2020 •

I think they even came back before the request. I tried to follow the migration advice from this guide.

We are still on legacy though:

travis-ci.org
Screenshot_20200818_165015

travis-ci.com
Screenshot_20200818_165356

Nothing broken yet. Please tell me when I am moving too fast!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants
You can’t perform that action at this time.