-
Notifications
You must be signed in to change notification settings - Fork 44
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
CI: Remove Travis builds #1792
CI: Remove Travis builds #1792
Conversation
We've now migrated to GitHub Actions with good results after running for 1 to 2 months.
Drats! And GHA then goes to fail with it's unique case I've seen a couple of times. On uploading the artefacts, it sometimes fails, which means the tests then can't get access to the installer to test against. But for some reason, even when artefact upload fails, the task is marked as successful but you see this in the logs:
Anyway, I've restarted the build. 😞 If this continues in the future, we can raise an issue against the action - or it seems like it could be actions/upload-artifact#71 |
Looks okay now, just failed a known flaky test. HierarchyTopicTest. Probably fine to merge. |
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.
I think we can also remove travis related files in autotest
such as travis.conf
and yaml files (e.g. testng-travis-contribution.yaml
)
Good point @PenghaiZhang , I'll do that now(ish). |
If I get green on GHA and CodeBuild, I'll merge on in. |
Checklist
Description of change
We've now migrated to GitHub Actions with good results after running for 1 to 2 months. So as per the CDM decision, let's remove Travis (starting here on develop only - will keep on older stable branches etc).