Releasing new versions of our services is done by Travis CI. Travis first runs our test suite. Once it passes, it publishes a new release binary to GitHub.

Common tasks such as installing dependencies for the Go project, or building a binary are automated using plain old Makefiles. (We know, crazy old school, right?) Our binaries are compressed using UPX.

Travis has come a long way over the past years. I used to prefer Jenkins in some cases since it was easier to debug broken builds. With the addition of the aptly named “debug build” button, Travis is now the clear winner. It’s easy to use and free for open source, with no need to maintain anything.

#ContinuousIntegration #CodeCollaborationVersionControl

READ LESS
Stream & Go: News Feeds for Over 300 Million End Users - Stream Tech Stack | StackShare (stackshare.io)
23 upvotes·1 comment·82.3K views
Martin Delille
Martin Delille
·
September 14th 2018 at 12:35pm

I prefer Gitlab CI.

·
Reply