6 ms·
>requiring some development to put those tools to use The best CI is the one where you write code to build/deploy etc. Wrangling with some moronic UI exposed
by mariusmg 9y ago
>requiring some development to put those tools to use
The best CI is the one where you write code to build/deploy etc.
Wrangling with some moronic UI exposed by the CI product to abstract code is simply wrong. Don't do CI/CD like this.
- gabrielr 9y agoRight. One of my favorite parts of Concourse is that all the config is declarative, in YAML that teams can (and do) check into a public Git repo (with the secrets kept elsewhere). That lets teams share Concourse task and resource definitions. Many teams (including mine) publish our pipeline definitions too [0]. This enables "tooling" type teams build components that get a lot of re-use by other teams. disclaimer: I work for Pivotal. [0] e.g. code.cloudfoundry.org/cf-networking-ci
- witten 9y agoSome development is fine (and expected). And indeed the goal of "build automation" was what led us to evaluate both Concourse and GitLab. We were previously on Bamboo, which really did require wrangling with a moronic UI. But I think there's a difference between a mostly complete CI product with API extension points, and a "batteries not included" CI toolbox.