-
Bug
-
Resolution: Answered
-
High
-
None
-
None
-
None
we've some quite important but not urgent deployment scheduled to run at 4 in the morning
we've set this time, as no devs are up and coding, thus we are not delayed by these deployments
moreover, we've our elastic instance set up to shut itself down after some period of inactivity (we definitely don't want to run them all night)
as a result, there is no running instance at 4am when the deployment should happen
unfortunately, Bamboo does not start a new instance, thus our deployments can not run until the morning when we make our first commit, just the time that we wanted to avoid.
- relates to
-
BAM-13588 Deployment projects don't start EC2 instances automatically
-
- Closed
-
[BAM-14824] Bamboo Deployments should start a new EC instance if there is no instance running
Workflow | Original: Bamboo Workflow 2016 v1 - Restricted [ 1442718 ] | New: JAC Bug Workflow v3 [ 3384399 ] |
Status | Original: Resolved [ 5 ] | New: Closed [ 6 ] |
Workflow | Original: Bamboo Workflow 2016 v1 [ 1420127 ] | New: Bamboo Workflow 2016 v1 - Restricted [ 1442718 ] |
Workflow | Original: Bamboo Workflow 2014 v2 [ 702821 ] | New: Bamboo Workflow 2016 v1 [ 1420127 ] |
Fix Version/s | New: 5.6.0 [ 40496 ] | |
Fix Version/s | Original: 5.7 [ 40495 ] |
Fix Version/s | New: 5.7 [ 40495 ] |
Resolution | New: Answered [ 9 ] | |
Status | Original: Needs Triage [ 10030 ] | New: Resolved [ 5 ] |
Hmm, I think 5.6 is the correct one.