Ask HN: How do you deal with distribute CI definitions?

Posted by throwawayci on Friday July 06, 2018 @11:08AM
from the ask-hn dept.

With the move to CI configuration files stored on each repository (.travis, .buildkite, Jenkinsfile, etc) versus a central location. How do you deal with keeping all pipelines standardized? Do you have a central CI team that touches all these repos (and has the autonomy to do so)? Or is it up to developers to keep things updated? Say you want all pipelines to have a linting step, how would that happen in your organization?

( 2 comments | 4 points | on HN )

Re:Ask HN: How do you deal with distribute CI definitions? by fatninja on Saturday July 07, 2018 @04:31AM (#17477673)

We provide very generic CI templates for each stack(java,go etc). If teams want any customizations on top of that, they will have to do it themselves. In CD we have some very specific expectations from the package so this make sure that CI part won't go way out of the way even if they make some customizations.

[ Parent | on HN ]

Re:Ask HN: How do you deal with distribute CI definitions? by ilotro on Friday July 06, 2018 @11:15AM (#17472083)

We leave it to each team to write and manage their own, gently nudging them in the right direction if they stray.

[ Parent | on HN ]