CI/CD is the way!
Pros
- Pipeline-as-Code works really well. All our pipelines are defined in yml files, which are checked into SCM.
- The ability to link multiple pipelines together is really cool. Later pipelines can declare a dependency to pick up the build artifacts of earlier ones.
- Agents definition is really great. We can define multiple different kinds of environments to best suit our diverse build systems.
Cons
- I miss the ability to have custom build parameters on GUI. So, all the changes even the smallest ones have to be checked into SCM.
- If there's an ability to define the priority of the pipelines, that would be great. Some build environments only have a couple of agents, so there are times that builds have to wait for quite a long time.
- I wish that I can create a new view for a group. Currently, if I have a view for group A, then more pipelines are added to that group, I have to edit the view to manually add the new pipelines.
Most Important Features
- Pipeline-as-Code
- Automatic triggers
- Clean & clear GUI
Return on Investment
- Automated CI/CD improves quality tremendously
- People can spend time on more interesting activities instead of repeated tasks
- Peace-of-mind when the changes are well-tested multiple times
Alternatives Considered
Jenkins
Other Software Used
IntelliJ IDEA, Bitbucket, Atlassian Confluence
