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.

Sign up for GitHub

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

feat(ci): update cargo gen to 0.2.2 #34

Open
wants to merge 4 commits into
base: master
Choose a base branch
from
Open

feat(ci): update cargo gen to 0.2.2 #34

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
3cc656b
feat(ci): update cargo gen to 0.2.2
ashleygwilliams Dec 27, 2018
217390a
feat(ci): log cargo gen version
ashleygwilliams Dec 27, 2018
a3cc48d
debug: pwd
ashleygwilliams Dec 28, 2018
8f80944
debug: git status
ashleygwilliams Dec 28, 2018
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 4 additions & 1 deletion .travis.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -14,10 +14,13 @@ matrix:
chrome: stable
before_script:
- (test -x $HOME/.cargo/bin/cargo-install-update || cargo install cargo-update)
- (test -x $HOME/.cargo/bin/cargo-generate || cargo install --vers "^0.2" cargo-generate)
- (test -x $HOME/.cargo/bin/cargo-generate || cargo install --vers "0.2.2" cargo-generate)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If we get a cached cargo-generate, and therefore don't execute the updated cargo install command here, whill cargo install-update -a bump minor versions of an installed tool? If not, we may need to do two pushes: one that doesn't use any chached tool to force an install of 0.2.2, and then another to re-enable the use of cached tools. I think I've been bitten by this before. Not sure what the best way to deal with this is going forward.

- cargo generate --version
- cargo install-update -a
- curl https://rustwasm.github.io/wasm-pack/installer/init.sh -sSf | sh -s -- -f
script:
- pwd
- git status
- cargo generate --git . --name testing
# Having a broken Cargo.toml (in that it has curlies in fields) anywhere
# in any of our parent dirs is problematic.
Expand Down