Continuous Deployment Isn’t Just for Applications
While we’ve been pushing more of our production services towards Continuous Deployment for faster and safer releases, we’ve discovered we can build the ideas of Continuous Deployment into our culture and all areas of our stack.
Co-authored by Leigh McCulloch
Cross-posted to Braintree’s Product and Technology Blog: Continuous Deployment Isn’t Just for Applications
We now continuously deploy important internal libraries written in both Ruby and Java, and plan to ramp up this effort to include internal tools as well. The process our engineers go through when contributing to shared libraries looks like this:
- Developers check out the shared library and make their changes
- Developers open a pull request
- Jenkins tests, builds, and publishes a test version of the library
- Pull request is reviewed and iterated upon
- While iterating, developers can upgrade to the test version in one or more applications using the shared library
- Once the pull request is merged, Jenkins publishes a new version of the library
- Developers can then upgrade the library in the applications
We’ve found that Continuously Deploying our libraries has eliminated repetitive tasks and helped us move quickly with shared code initiatives where a monolithic repository was not an option. New engineers can now easily integrate and contribute to libraries by reading simple scripts rather than long documentation describing our release processes. Deploying test versions from open pull requests has given engineers the ability to iterate on functionality spanning applications and shared libraries without needing to merge to master early.
Here are the steps we took to make this process as easy as possible.
The first big question was how to version libraries. For semantic versioning we’d use
v2.3.1) but that doesn’t work as well when you are releasing every commit of the master branch.
We’ve iterated a few times on the versioning, and our current version scheme looks like
major.datetime.description.git_revision. For example, a version for consumption might be
4.20181210231852.master.ef57297 whereas a pull request might be
- Major version: We use a major version of
0for testing versions. And we only increment the major version when making backwards incompatible changes.
- Pull request number: If this is a pull request, we include the pull request number.
- Date: The date serves two purposes. First, it ensures that newly published versions sort higher than older versions. Second, it allows you to get a sense of how old the library is at a glance without looking up the git revision
- Description: We add the word
masterfor master builds and
prfor PRs. We do this to clearly signal where a version has been built from. While we use the major versions to signal this as well it’s much clearer to a human to see the description.
- Git revision: This allows us to know exactly which version of the code generated this release.
We also wanted to encourage engineers to iterate on changes in a shared library without merging their work-in-progress to master too early. We wanted to make working across shared library boundaries as simple as possible.
To support this behavior, we build and publish a version of each shared library on every pull request with a version that never supersedes master builds. We use a major version of
0 to signal the build is not a release for the current or a future major version. We use a minor version that matches the pull request number so that consumers of the library can pin to that minor version to get updates to their pull request.
Our build system posts a comment back to the pull request with the published version to ensure new engineers discover this workflow immediately.
Jenkins posting a message to our pull request
Using the library
Our versioning schema means that a ruby consumer of the library can pin themselves to a major version and pick up upgrades without breaking their integration.
For example, this would reference the latest version in in a ruby Gemfile by using the tilde operator:
gem "mylib", "~> 2.0"
For pull requests, it looks like this in the ruby Gemfile:
gem "mylib", "~> 0.89.0"
In ruby, this means you can update the library to the latest release in the current major version with
bundle update mylib.
Consumers are also welcome to pin to the specific version, such as this in ruby:
gem "mylib", "4.20181210231852.master.ef57297"
And in a maven pom.xml:
<dependency> <groupId>braintree</groupId> <artifactId>mylib</artifactId> <version>4.20181210231852.master.ef57297</version> </dependency>
We’re converting more of our libraries and internal tools to this approach. Let us know how you’re building Continuous Deployment into your culture!