Hello, I don't think there is any way to do that. The reason why older builds can be advanced is that when something is wrong with a newer build in production, one would want the ability to switch back to the older stable build.
Since, the stage to deploy to production is manually triggered in your case, can you tell me why you would want to completely disable it as well? If someone does accidentally push the older build to production, you an always rerun the 'ProductionDeploy' stage to deploy the newer build. Granted that this is more effort, but deploying a wrong build seems like a one off case anyway. Thanks, Varsha On Wednesday, 3 May 2017 16:48:45 UTC+5:30, jetxs wrote: > > I've been using GoCD for a long time now, and it's great. However, I can't > figure out how to disable an older build from proceeding when a newer build > exists. (See attached img) An older build can still be manually advanced. > > Is this doable? > -- You received this message because you are subscribed to the Google Groups "go-cd" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
