Jenkins, the build masterhttps://www.trustradius.com/build-automationJenkinsUnspecified8.32481012019-10-18T17:45:24.682Z
October 18, 2019
Jenkins, the build master
Score 8 out of 101
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.
- 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.
As with all open source solutions, the support can be minimal and the information that you can find online can at times be misleading. Support may be one of the only real downsides to the overall software package. The user community can be helpful and is needed as the product is not the most user-friendly thing we have used.
Do you think Jenkins delivers good value for the price?
Are you happy with Jenkins's feature set?
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?
Would you buy Jenkins again?
Jenkins helps the flow of build from the development team to the QA team. Can be really helpful in doing continuous builds, but when this feature is turned on the development team must have great communication otherwise the risk of broken builds become very high. In the long run, we found it made things easier when we just pushed the build manually and appointed a team member the build master.
Like to use
Feel confident using
Difficult to use
Requires technical support
Slow to learn
Lots to learn