letsencrypt
/
boulder
mirror of https://github.com/letsencrypt/boulder.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
boulder/test/boulder-tools
History
Daniel McCarney fa9a79b55f
CI/Dev: Remove Go 1.10.2. (#3761) 
We've migrated the production/staging Boulder instances to builds using
Go 1.10.3 and can now remove the Go 1.10.2 builds from the travis matrix
and the `tag_and_upload.sh` Boulder tools script.
 		2018-06-14 12:04:29 -04:00
..
Dockerfile.tmpl Tools: Support multiple Go versions in CI/Dev. (#3622) 2018-04-05 14:08:54 -07:00
README.md Cleanup .travis.yml (#3691) 2018-05-04 19:32:30 -04:00
build.sh Remove boulder-tools checkout of mockgen/model. (#3455) 2018-02-19 09:02:55 -05:00
tag_and_upload.sh CI/Dev: Remove Go 1.10.2. (#3761) 2018-06-14 12:04:29 -04:00

README.md

Boulder-Tools Docker Image Utilities

In CI and our development environment we do not rely on the Go environment of the host machine, and instead use Go installed in a container. To simplify things we separate all of Boulder's build dependencies into its own boulder-tools Docker image.

Go Versions

Rather than install multiple versions of Go within the same boulder-tools container we maintain separate images for each Go version we support.

When a new Go version is available we perform serveral steps to integrate it to our workflow:

  1. We add it to the GO_VERSIONS array in tag_and_upload.sh.
  2. We run the tag_and_upload.sh script to build, tag, and upload a boulder-tools image for each of the GO_VERSIONS
  3. We update .travis.yml, adding the new Go version to the go section.

After some time when we have spot checked the new Go release and coordinated a staging/prod environment upgrade with the operations team we can remove the old GO_VERSIONS entries and delete their respective build matrix items.