Here's a breakdown of what we do on the chef/rundeck side:
We don't use jenkins but we use teamcity and execute deploys via rundeck API either through predefined jobs:
Or via ad hoc jobs:
curl -H "X-RunDeck-Auth-Token: FAKETOKEN" --data-urlencode "exec=sudo /usr/local/bin/vastexec -p PRODUCT -r RELEASE -e ENVIRONMENT"
This doesn't cover everything you asked, but I hope it helps.
On Friday, April 8, 2016 at 8:01:26 AM UTC-5, Sai Teja Penugonda wrote:
Any documentation?
Thanks. :)