Overall Satisfaction with Jenkins
Jenkins is been use as our main CI/CD software, we have a micro-service architecture that is been build, tested, deployed through all our environments qa, staging, production and all of them at scale. We also build on jenkins our mobile applications with the same flow we build test and deploy our applications to the stores reducing human error on configurations and spotting issues before we even know about it. That allow us to reach an estate of trust with our clients.
About Jenkins we are using the new BlueOcean interface, what it is really amazing; and using Pipelines as our definition language.
About Jenkins we are using the new BlueOcean interface, what it is really amazing; and using Pipelines as our definition language.
- Integration with third part tooling, testing software and platforms
- Plugin platform, really flexible and easy to develop for
- Open source
- Scalable
- Easy to install and configure
- UI Interface
- API
- Administration
- Reduce of set costs for CI/CD platforms
- Reduce of errors on the whole system is directly related to more incomes
- Ensure quality on our code that is also related to incomes
Basically all those CI/CD tools provides the same set of tooling. SaaS solutions have a pre set pool of languages and containers you can use, but hey also are less flexible because they will not allow you to do advance configurations or setups you may need.
With jenkins you have the full power of the tool on your hand so there is no limit on what you can do
With jenkins you have the full power of the tool on your hand so there is no limit on what you can do