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

TravisCI Mac builds no longer free #1276

Closed
ja2-derek opened this issue Nov 7, 2020 · 8 comments · Fixed by #1291
Closed

TravisCI Mac builds no longer free #1276

ja2-derek opened this issue Nov 7, 2020 · 8 comments · Fixed by #1291
Milestone

Comments

@ja2-derek
Copy link
Member

Heads up to the new TravisCI pricing model. I understand they no longer run Mac builds for free.

https://blog.travis-ci.com/2020-11-02-travis-ci-new-billing

Maybe we should look at building nightly with GitHub action again

@lynxlynxlynx
Copy link
Member

Appears so, let's migrate.

@ja2-derek
Copy link
Member Author

ja2-derek commented Nov 7, 2020

I believe the easiest way is to make the nightly push with a Personal Access Token (see also #873 (comment)). To proceed, I need an org admin to add the tokens as encrypted secrets:

  1. Personal Access Token from any user with repo write access (maybe @madlab-bot ?). This token is used to push nightly branch, or directly run the workflow via GitHub API if push still doesn't work.

  2. Coverity scan token. We can migrate the coverity build into another scheduled GitHub Action. Something like this.

@ja2-derek ja2-derek linked a pull request Nov 15, 2020 that will close this issue
@ja2-derek ja2-derek removed a link to a pull request Nov 22, 2020
@lynxlynxlynx lynxlynxlynx added this to the v0.18 milestone Nov 22, 2020
@ja2-derek
Copy link
Member Author

A Coverity scan was successfully submitted earlier today (build). But the Coverity dashboard is still not updated, and the badge still says "Coverity Failed".

Are you able to get any further information from Coverity side?

@lynxlynxlynx
Copy link
Member

You should have the same access, but anyway, it says the last ok build was in october and anything later failed due to compilation errors:

Last Build Status: Failed. Your build has failed due to the following reason. Please fix the error and upload the build again.

Error details: 
invalid literal for int() with base 10: "tail: cannot open '/opt/workspace/ja2-stracciatella_ja2-stracciatella/cov-int/build-log.txt' for reading: No such file or directory

Like the results weren't successfully submitted, even though the upload was fine.

@ja2-derek
Copy link
Member Author

That explains it. Thank you.

But where do you get that error details?

@lynxlynxlynx
Copy link
Member

@ja2-derek
Copy link
Member Author

Nothing for me. Probably admin-only.

There are only the Coverity Scan badge and then the heading "Analysis Metrics".

@lynxlynxlynx
Copy link
Member

Now that it's fixed for sure. I've upped your privilege level, so if it ever happens again, you'll hopefully see it.

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

Successfully merging a pull request may close this issue.

2 participants