-
Suggestion
-
Resolution: Duplicate
-
None
-
None
I would like an option on the deployment plan's scheduler to not trigger a deployment if there has been no new code updates to the parent plan.
Current world, if I set up a cron trigger to deploy hourly from FOO-BAR build plan, it will continue to deploy every hour even if there is no change to FOO-BAR. (Essentially, deploying FOO-BAR-12 artifact over and over and over)
I see how this may be desirable for some users, but our use case for this improvement is that a deployment to our QA environment leads to about 5 mins of downtime as the servers all re-initialize. We want to only incur that cost if there is something new to deploy, and know through cron that it will only happen at most on the hour every hour.
- is duplicated by
-
BAM-14932 Configure Deployment On Schedule If Change
- Closed
- is related to
-
BAM-15918 Add a Option on Deploy Triggers to execute only when there is a newer build
- Closed
- relates to
-
BAM-14311 Scheduled deployments should only run if the latest version is different than what is actually deployed in that environment
-
- Closed
-
[BAM-14916] Deployment trigger scheduler should have option to not deploy the same code
Workflow | Original: JAC Suggestion Workflow [ 3016305 ] | New: JAC Suggestion Workflow 3 [ 3602375 ] |
Status | Original: RESOLVED [ 5 ] | New: Closed [ 6 ] |
Workflow | Original: Confluence Workflow - Public Facing v4 [ 2703685 ] | New: JAC Suggestion Workflow [ 3016305 ] |
Issue Type | Original: Improvement [ 4 ] | New: Suggestion [ 10000 ] |
Workflow | Original: Bamboo Workflow 2016 v1 [ 1417405 ] | New: Confluence Workflow - Public Facing v4 [ 2703685 ] |
Workflow | Original: Bamboo Workflow 2014 v2 [ 721784 ] | New: Bamboo Workflow 2016 v1 [ 1417405 ] |
Resolution | New: Duplicate [ 3 ] | |
Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
Component/s | New: Deployments [ 19692 ] | |
Status | Original: Needs Triage [ 10030 ] | New: Open [ 1 ] |