Move CI to trust #122
Move CI to trust #122
Conversation
|
Thank you for the PR! The nightly channels seem to be consistently failing to build. Could you have a look at why? |
|
@Aaronepower Sure! It seems to be a recent issue with rustup: rust-lang/rustup#1092. I'll keep checking till it gets resolved. |
|
I've enabled EDIT: if the CI tests pass, I'll do a rebase and squash all these commits to clean it up a bit. |
These changes configure the trust template to use the correct credentials and project name. The rest was left as is. There seems to be an issue with rustup at the moment rust-lang/rustup#1092. As suggested in rust-lang/rustup#1092 (comment) I've enabled the `allow_failures` feature for nightly builds.
alexeyzab
force-pushed
the
move-ci-to-trust
branch
from
3725ac2 to
3291ed9
Compare
|
This looks great! Could you also add a beta channel, so we can know ahead of time if tokei has a soundness bug or anything similar before it hits stable. |
|
Done. Let me know if there is anything else I can help with here. |
|
@alexeyzab Sorry, we want betas to give us an error on failure. I'm also not seeing any beta builds in either travis or appveyor? |
|
@Aaronepower My bad, I'll look into that. |
|
I've added beta channels back in for both travis and appveyor. I took all the targets from the old .travis.yml. |
|
Thank you! |
These changes configure the trust template to use the correct
credentials and project name.
This is an initial pass at setting up the new CI. If there are any
addition tweaks that need to be done here, let me know.
Thanks!
#120