Take the 2-minute tour ×
Programmers Stack Exchange is a question and answer site for professional programmers interested in conceptual questions about software development. It's 100% free, no registration required.

I know that Jenkins is focused on continous building/testing, monitoring of batch jobs about the project. We have a legacy project which such condition :

1)Has a development team.

2)It has SVN for source code management

3)Some cronjobs for some operations.

4)Compile&Build don't take too much time, there is no very complex dependencies.

5)It doesn't have any automated test/junit classes and will not have.

I'd like to ask to experienced users about Jenkins, is it still worth to use Jenkins for central build&management of the project ?

share|improve this question
2  
Jenkins will allow you to have clean-room builds. This is invaluable for reproducability. –  user1249 Feb 2 '12 at 14:21

3 Answers 3

up vote 6 down vote accepted

It is worth it, as others have said, just for the stable, automated build process itself. But just having it and in use could begin to change some internal practices you didn't even know you wanted to change in the first place (not saying that's your situation, just that it's possible).

Case in point, I recently managed a group that, over the course of the year, went from nearly the same type of environment as you listed to one that incrementally used more features of CI (Jenkins, specifically) and to their benefit. For instance, the group switched from a mix of SVN and git to a mix of public and private GitHub repos with post-commit hooks back to Jenkins, allowing them to better distribute and manage their different types of projects. Additionally, test coverage improved -- included going from none to some, and from some to much more -- including from some folks who just didn't like writing tests, because seeing everyone else's tests break or not made them feel like they had to keep up and/or join the fun (this was a neat thing to watch, don't know how common it is!). Deployment moved from batch scripts and manual processes to push-button deployment of builds, with an eye toward never doing it the "old way" again.

Like most tools, it'll only be as useful as you make it, but even if you use it for the most minimal reasons, I'm a Jenkins fan.

Edited to add: Apropos of nothing, today is Jenkins's birthday.

share|improve this answer

I'd like to ask to experienced users about Jenkins, is it still worth to use Jenkins for central build&management of the project ?

Definitely. Even if you don't/won't use Jenkins to run any automated testing, it is still a valuable tool. What you still get out of it is a neutral party that will continuously attempt to build your software and will notify you and your team if it is unable to do so. This is very valuable as it prevents an unstable build of your software from going unnoticed.

share|improve this answer

It's definitely worth it. One often un-noticed benefit is that it forces you to have your build process automated, which is a huge win just by itself. Regardless of the build stability, simply having it all automated is usually the hardest step, so if using jenkins encourages that and helps tto enforce it, the it's worth it.

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.