Quick deploy in pipelines
It would nice to be able to use the Quick Deploy feature once a release is validated, instead of either hitting deploy or scheduling the deploy and having it validate one again.
Kayla
shared this idea
-
Peter Twomey commented
Adding my vote to this one. The double validation and running of tests make some deployments take a huge amount of time, which leads to poor practices being undertaken for hotfixes, as sometimes there simply isn't enough time to wait for another deployment to run. I would at least like the option, as it should be my responsibility to ensure the validation is still accurate before I attempt to deploy.
-
Jonathan Flatt commented
Agree with Jason's comment on bypassing the promotion pre-validation option in the CI job settings. It would save a considerable amount of time in busy orgs.
-
Kyle Varga
commented
Eric - Salesforce will remove quick deploy option (so Gearset would then fall back to full deployment). Right now we see a huge delay with:
1. Gearset validation
2. Salesforce validate-only deployment
3. Merge Request / Repo Merge
4. Full Salesforce Deploy.At minimum, quick deploy should be able to be used for the 4th step.
-
Jason Miller
commented
Would be valuable to have a setting where we could bypass the pre-deployment validation that occurs automatically when a branch is merged. We validate when the PR is created (per the setting provided on the CI job) and we can fix it if the job somehow fails. Just want the option to bypass and manage the process ourselves. It saves up to an hour on Prod deploys so especially useful there.
-
[Deleted User]
commented
this requires detection that the org hasn't changed in the interim