Posted on: 15/10/2019
Some quick thoughts on what I remember about all these CICD systems.
Gitlab (Rating 4/5):
- Feels massively comprehensive
- You can host your own “runners”
- The documentation can be all over the place. Specially with the gitlab issues - where solutions / workarounds are mixed in with hundreds of other comments
CircleCI (Rating 4/5):
- Setting environment variables are done ONE AT A TIME. So many clicks… It’s really tedious.
Google Cloud Build (Rating 4/5):
- Real nice that you can set custom instance types - for example if you wanted instances with more CPU / memory - it’s just a single line to specify this
Bitbucket pipelines (Rating: 3/5):
- Really simple
Travis (Rating: 1/5):
- They request your GITHUB USERNAME AND PASSWORD if you want to use “encrypted variables” in your travis build file!?!? https://stackoverflow.com/questions/49365669/travis-ci-enterprise-travis-encrypt-after-successful-login-responds-not-logg
- Documentation seems bad. Concepts are really not well defined.
- An annoying issue that hasn’t been fixed in months https://github.com/travis-ci/travis-ci/issues/6652
- Another annoying issue where tagged commits get built as a separate git branch https://stackoverflow.com/questions/30156581/travis-ci-skipping-deployment-although-commit-is-tagged. This makes 0 sense because, if it’s built as a branch, then all your “branch specific” environment variables aren’t set?
No comments, yet!