Overall Satisfaction with Jenkins
We use Jenkins as our build management software, and it is mostly used between the development and QA teams. We use it both in manual and automated builds. It allows the developers to work together and send a combined solution to the QA team. It also controls our versioning with minor builds and patches.
- Automated build process
- Great process control
- Good notifications to groups
- Can be difficult to configure
- Not the best error reporting
- Helps with workflow really well.
- Investment is really only time as it is open source.
- Azure DevOps (formerly VSTS)
Team services, while very similar, did not really have that much more added features for the much higher price tag. The team has moved over to the subscription-based Visual Studio so we may be reevaluating this solution as now it is part of our subscription and no longer an added cost.
Do you think Jenkins delivers good value for the price?
Yes
Are you happy with Jenkins's feature set?
Yes
Did Jenkins live up to sales and marketing promises?
I wasn't involved with the selection/purchase process
Did implementation of Jenkins go as expected?
Yes
Would you buy Jenkins again?
Yes
Using Jenkins
6 - The software is used by our developers and our AQ analysts.
1 - We have one of our developers with a IT background and he manages all our DevOp work.
- Build management
- Build notifications
Using Jenkins
Pros | Cons |
---|---|
Like to use Consistent Feel confident using | Unnecessarily complex Difficult to use Requires technical support Slow to learn Cumbersome Lots to learn |
- Pushing out a build
- Setting up new projects
- Setting up notifications