Overall Satisfaction with Jenkins
Jenkins is the frontline tool used by our Device Integrations team to ensure a smooth release process for each version of our app, whether that is doing a feature build for our QA team, uploading a new version for release day, or simply making sure each new PR builds and passes our test suite before merging into our main build branch.
- Full customization with a complete library of plugins and raw shell build steps
- Credentials handling with built-in storage
- Custom environments with locally hosted instances
- The UX is messy compared to other solutions
- Jenkins doesn't have the best method of storing job configs in its related repo, unlike GitHub Actions or CircleCI
- You can't easily set an environment variable for the rest of your job from within a build step, if at all.
- Freestyle builds for releases
- Permission levels
- Triggered builds for pull requests
- It automates the release process, making is easier, faster, and most consistent.
- It takes quite a bit of work to maintain, sometime delaying builds by a day or so to get the issue sorted out.
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?
I wasn't involved with the implementation phase
Would you buy Jenkins again?