Jenkins provides solid support for Continuous Integration and Continuous Delivery
April 09, 2018
Jenkins provides solid support for Continuous Integration and Continuous Delivery
Score 8 out of 10
Vetted Review
Verified User
Overall Satisfaction with Jenkins
Jenkins is currently used to build and deploy our Amazon infrastructure. We practice the principles of infrastructure as code, meaning our infrastructure config and setup is checked into a revision control system and built via Chef and other scripts. Jenkins manages building that automatically or on demand and ensures that everything that is checked in is working properly.
- Configurability - Jenkins supports all sorts of options for different build types (Microsoft, Unix, etc.).
- Performance - The Jenkins user interface responds pretty well and can handle a number of projects.
- Plugins - Generally if you have a third party system to integrate with, Jenkins generally has a plugin for it.
- User Interface - The UI feels a bit dated and can be hard to use at times.
- Error messaging could be friendlier - sometimes it can be hard to decipher what went wrong.
- Configuration of roles could be easier. It would be nice if it was easier to give access to certain users for certain build options/projects/etc.
- Streamlined building our server infrastructure, which gave us more time for other development efforts.
- Helped improve code quality - we were able to verify that the code was compiling properly with each check-in.
- Made deployments more bullet proof - with a standard flow for deploying our code/infrastructure, it made less room for human error.
TeamCity is another viable option for Continuous Integration/Development. We picked Jenkins in this case because there was a lot of support for Amazon CloudFormation and other AWS integrations which fit the task at hand. For just straight compiling Microsoft based builds, TeamCity was a bit easier to use but was a bit more lacking in the AWS build options.