-
Notifications
You must be signed in to change notification settings - Fork 250
Configuring auto deploy
Tyler Ouyang edited this page Sep 22, 2023
·
4 revisions
- Navigate to your environment, click "Configure", and then "Auto Deploy".
- Select AUTO in 'Promote Type'.
- Select preceding stage, where the deploy comes from.
- BUILD is a special stage standing for new builds.
- Specify different actions upon auto deploy failures:
- CONTINUE: this is the default behavior. Builds will continue to be promoted from pred stage to the current stage .regardless of deploy failure
- ROLLBACK: will automatically roll back to preceding stage upon deploy failure.
- DISABLE: will stay in the failure deploy until manual intervention.
- Specify how auto promote should be disabled when someone manually creates a deploy:
- AUTO: This is the default behavior, auto promote will be disabled automatically when there is manual deploy.
- MANUAL: auto promote can only be disabled explicitly.
- Specify when Auto Promote should happen.
- Unix cron-like syntax. see http://www.quartz-scheduler.org/documentation/quartz-2.x/tutorials/crontrigger.html for more details on actual syntax
- A real example, to disable auto deploy between utc midnight and utc 8 am, set the schedule as: * * 0,8-23 * * ?
- If set Queue Size to 1, the latest build or deploy in the promote queue will be chosen; otherwise, the nth build from the top in the promote queue will be chosen.
- Make sure the branch in the stage configuration matches the branch of builds.