Powerful CICD tool for handling all stages in pipeline with versatile programs.
Overall Satisfaction with Jenkins
We use Jenkins as a main
CICD in our project, we organize jobs with similar function into Group, we
create jobs for the build, compile, and unit test each time a developer
check-in their code to a specified branch and build a new version of artifact
when having master branch commit.
We add some additional
plugin and create Jenkins jobs for run system test, automation test, and
integration test automatically when having new commit to master and have jobs
for deploy our new code to destination VMs on demand.
CICD in our project, we organize jobs with similar function into Group, we
create jobs for the build, compile, and unit test each time a developer
check-in their code to a specified branch and build a new version of artifact
when having master branch commit.
We add some additional
plugin and create Jenkins jobs for run system test, automation test, and
integration test automatically when having new commit to master and have jobs
for deploy our new code to destination VMs on demand.
Pros
- continuous deployment
- continuous integration
- continuous delivery also it's the best integration tools in the market
Cons
- Jenkins UI looks bit classic, and it is hard for manage when we have a large number of jobs and pipeline
- It does not have features for tracking job history, sometimes accident deletes or changes to a job and we unable to recover it.
- User and roles management needs some improvement
- It made very good impact in business by fastening the process
- It provides single place for building all the jobs
- I don't see any negative impact from Jenkins
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?
Yes
Did implementation of Jenkins go as expected?
Yes
Would you buy Jenkins again?
Yes

Comments
Please log in to join the conversation