-
-
Notifications
You must be signed in to change notification settings - Fork 6.9k
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 Travis jobs to travis-ci.com #2938
Comments
hey, can I have this issue? |
Sure, give it a try. Though I have little knowledge of Travis myself and we only use it, because they offer some compiler versions nobody else do. I guess there are some documentation how to move projects, though I'm not sure whether this needs my credentials. Just try! |
Hey @nlohmann I build jobs on travis-ci.com what to do now ? |
I assume you forked the project and edited the YAML file for Travis? If so, please open a pull request. |
@akbhuker FYI I just logged into travis-ci.com and could "migrate" my projects. Now I can see all previous builds there, but new builds are not triggered on new commits. |
ok what should I do now? |
Can you comment on #2940 (review) ? If your change is more than converting YAML to JSON, then maybe I need to merge these changes to take effect. Otherwise, I'd need to contact the support of Travis. |
I think merge these changes help you in to triggered build on new commits. |
HI @nlohmann would you now able to trigger builds on new commits |
@akbhuker I found the reason the projects did not build on travis-ci.com after the migration. I forgot to set this switch: Now all there is left is to update the badge in the README. I will do this in a PR in a minute. Sorry for the inconvenience - I did not know that I basically just had to press some buttons in the Travis UI. |
The Travis jobs are currently not triggered as the jobs are not yet moved to http://travis-ci.com.
The text was updated successfully, but these errors were encountered: