It’s been a few months since this thread saw activity. Are there any updates?
My team is currently using a different CI, I’ll hint it starts with a J We’re considering to migrate our builds into cci but the lack of this feature stops us.
Why we need it so badly? We’re a small startup and we have’t got to create sufficiently thorough tests suits. Since we don’t want to break master branch unnecessarily, we manually merge pull requests, and we manually promote production bundles. Basically, we control the deployment of builds to some of our aws elastic beanstalk environments (not all of them, some are still automated).
One of various scenarios: we have a build job for pull requests which doesn’t auto-deploy and test. Our qa team goes thru the PRs, deploys them into one of few aws beanstalk environments, tests it. Then moves to the next PR…
The option of kicking off an automated deployment from a circle-ci build (as mentioned by @casshill ) would be perfect for us. Seems it could be facilitated by adding a button which triggers a script run. The script can be defined in
circle.yml similarly to other run commands. The UI may provide a dropdown option to choose parameters to the script (this could be used to specify the aws ebs environment in our case, for example).
The ROI on such a feature is huge. It probably requires little dev-team effort, while providing the team with flexibility and fine-grain control over the build promotion process.
So, is it a good feature or a great feature?