JENKINS, OPEN SOURCE CONTINUOUS INTEGRATION TOOL
December 14, 2017
JENKINS, OPEN SOURCE CONTINUOUS INTEGRATION TOOL
Score 8 out of 10
Vetted Review
Verified User
Overall Satisfaction with Jenkins
In our EAI department, we are using Jenkins to automate building and packaging TIBCO BW project.
Once the testing step is OK, the package is installed firstly in test environment.
Jenkins process is triggred each time a code is commited on SVN.
Jenkins can also serve as a versioning system because each time a build is made, its version is stored in Jenkins
Once the testing step is OK, the package is installed firstly in test environment.
Jenkins process is triggred each time a code is commited on SVN.
Jenkins can also serve as a versioning system because each time a build is made, its version is stored in Jenkins
- Graphical Interface.
- Possibility to use versioning system like SVN,CVS.
- We can execute quality code tool to check code quality.
- Easy to install.
- Version change too fast can sometimes cause instabilities with some plugins that have not been updated yet.
- In an open source context, coordination between different developers is often lacking; suddenly, it's sometimes a bit of a mess: new versions come out quickly, but they are not always well tested and regressions appear.
- Win time by automating building
- Win time by automating packaging
- Win time by automating testing
- Win time by automating deployment
Jenkins is the only continuous integration tool used. So I can not evaluate other products