How to automate custom build tasks, eg, releases?

help
#1

Hello,

I’d like to automate my release processes, but I am not sure about the best practice here. I understand that Cargo offers no “custom tasks”, so how do you implement custom build tasks in your Rust projects?

I know that I could just write shell (Python, Ruby, etc.) scripts and put these in my source code, but I’d rather prefer if I did not need to setup two (or even more) language environments to work on my projects—in particular on Windows.

So what’s your recommendation or best practice here?

Regards.

PS: I’m aware of cargo-release but it doesn’t suite my needs. It seems to be geared towards manual releases, whereas I’d like my CI to take care of publishing, etc. and only do essential things locally, in particular bumping the version and updating the changelog.

#2

You can do something like cargo new --bin tasks, and, write automation as usual Rust program, and then run it as cargo run --manifest-path ./tasks/Cargo.toml --bin task-foo. That way, you get a cross-platform “scripting” environment, which could use serde and other goodies from crates.io, provided that you have Cargo on the target machine.

If you add more hacks, you can even make it feel built-in: https://matklad.github.io/2018/01/03/make-your-own-make.html :slight_smile: We also plan to add something similar as a first-class feature to Cargo: http://aturon.github.io/2018/04/05/workflows/.

2 Likes
#3

Thank you very much; that’s a really nice idea. Also thanks for linking these two posts; learned a lot about Cargo in both!

#4

There is also cargo make which may also fit your use case.