3 ms·
We use Jenkins [1] for CI. Every team runs its own Jenkins instance and has an individually configured CI pipeline. The more we grow, the higher raises the wish
by moasda 7y ago
We use Jenkins [1] for CI. Every team runs its own Jenkins instance and has an individually configured CI pipeline. The more we grow, the higher raises the wish to unify the Jenkins CI/CD flow.
[1] https://jenkins.io/ https://jenkins.io/
- somada141 7y agoHave y'all had any maintenance/upkeep issues operating multiple instances?
- moasda 7y agoInitially, this approach had many advantages, because every team could individually configure its Jenkins instance and toolchain without being at risk to break each other's pipeline. This was just fine. After some while, when CI is running well, the focus goes away from CI to other fancy development things. So, updating and maintaining the CI pipeline becomes a more dull job and we think about replacing the individual CI pipelines by a unified one.