CircleCI Ideas

Re-run build with updated orb

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

  • Avatar32.5fb70cce7410889e661286fd7f1897de Guest
  • Dec 4 2018
  • Not planned
  • Attach files
  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    January 07, 2019 23:02

    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. 

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    January 07, 2019 23:12

    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?