Due to the way dependencies work with Cargo, this may not be applicable to building Rust repositories, since a fresh machine would need to rebuild dependencies from scratch every time, which takes too long. There may be some 'hacky' ways around this, such as doing a build in advance, copying the output of the build to a known location on the slave, then having the Jenkins pipeline copy that output to its working directory, but I'm not even sure that would work correctly.
It may be applicable for building other types of applications, so I think it's worth capturing.
Due to the way dependencies work with Cargo, this may not be applicable to building Rust repositories, since a fresh machine would need to rebuild dependencies from scratch every time, which takes too long. There may be some 'hacky' ways around this, such as doing a build in advance, copying the output of the build to a known location on the slave, then having the Jenkins pipeline copy that output to its working directory, but I'm not even sure that would work correctly.
It may be applicable for building other types of applications, so I think it's worth capturing.