Who says CLIs aren’t the sexiest part of a product? They are the backbone of DevOps and when it comes to automating your pipeline there is nothing better. In August we are rolling out a new CLI for Rancher, and we want to show you how to use it to automate all aspects of your delivery pipeline. In our July meetup, we talked Docker pipeline automation and how to use the new Rancher CLI to deploy applications, manage upgrades, infrastructure provisioning, troubleshooting and more.
We were also joined by Jason Greathouse, Director of DevOps Architecture at LeanKit, who will share how his team is running Docker in production. We've posted a full recording of the meetup on youtube(linked), along with these slides. You can also download an early release of the new CLI and try it out for yourself.
During Jenkins Build- make run-Jenkins 1m 10
This could be any CI, so longs as it can be run in a container and everyone can build in a consistent way then it doesn’t matter what its doing.
As part of this build it could be executing unit tests etc
I’ve mapped through the drive but you could just as easily have it git pull into the container, my instance monitors the remote git repo and then builds it from the mapped drive. There are pros and cons to both, I like this as I can make changes and run a manual build without needing to check in all the time.
Jenkins git build – 5 mins
Running multiple hosts locally causes pain as it means you need a repository or a means to get the built containers between the hosts. Overlay network also doesn’t currently work in boot2docker