Re-run build with updated orb
R
Ryan Keener
Right now it appears that re-building a previous job will continue to use the same orb version it used the first time. It'd be great to be able to have something similar to 1.0's "re-run without cache". Right now we're having to push empty commits to get the new build to use the newest orb version
CCI-I-750
R
Ryan Keener
I apologize for using the incorrect terminology but it does seem you understand my goal. Is this work already planned or is there another open Idea that I can add my vote to?
N
Nathan Dintenfass
Going to close this, as it's not really possible given the lifecycle of a build. It would also break the deterministic nature of a "Re-run". The broader problem to solve (which would be a different issue) is making it nicer to trigger a new build from the UI and/or from the CLI for changes like this.