Jenkins is a continuous integration (CI) system. CI systems are used to continuously test software so that failures can be detected, reported, and ultimately fixed quickly. BRL-CAD would like to have several CI systems set up to evaluate their usefulness for our open source community.
This task involves setting up Jenkins for BRL-CAD. At a minimum, Jenkins should be set up to test our configuration (cmake), compilation (make), distribution viability (make distcheck), performance (make benchmark), regression (make regress), and unit test status (make test).
You will also be required to document your progress installing and setting up Jenkins on our wiki (http://brlcad.org/wiki/Continuous_Integration) including all steps you take.
As this task requires accessing one of our development servers over SSH, you need to be comfortable working on a unix command line. Contact 'brlcad' in our IRC channel to get set up after claiming this task.
Resources:
- http://jenkins-ci.org/
| File name/URL | File size | Date submitted | |
|---|---|---|---|
| http://blog.moinnadeem.com/task-jenkins-ci... | n/a | December 02 2012 03:31 UTC | |
| http://crit.brlcad.org:8080/ | n/a | December 02 2012 03:32 UTC |
I would like to work on this task.
This task has been assigned to Moin Nadeem. You have 72 hours to complete this task, good luck!
Your access to crit.brlcad.org has been restored. Let me know if you have trouble getting in, but you should be able to set up Jenkins in your home directory's public_html folder (you may need to create this) as a demonstration. I can create a database for you if/when needed.
For some reason my home directory (/home/{myusername}) doesn't exist, and I cannot create it due to write permissions. I am going to the right place, correct? (cd ~ also leads there.)
Fixed.
The work on this task is ready to be reviewed.
Melange has detected that the deadline has passed and no more work can be submitted. The submitted work should be reviewed.
Congratulations, this task has been completed successfully.
Moin, thanks for your efforts getting it set up. I think the original description may have been a little over-ambitious, so I'm not holding that against you. ;) Thanks for the fantastic write-up too, that should help the next person continue, whether that's you or someone else. I do plan on creating another task in a couple days to set up our content specifically (our build and build tests) along with maybe other tasks for some of the items you identified in your post. Thanks again for your efforts!
A follow-on to this task has been posted:
http://www.google-melange.com/gci/task/view/google/gci2012/8109203
As GCI comes to a close, we wanted to take the time to say THANK YOU for all your efforts. This comment interface closes after GCI is over, so you're encouraged to join our mailing list where we'll be announcing contributions from GCI participants like yourelf over the upcoming months:
https://lists.sourceforge.net/lists/listinfo/brlcad-news
If you've provided your full name, we'll be sure to credit you in our authorship documentation and you'll see your name in a future announcement. If you contact us at devs@brlcad.org or via IRC, we'll even let you know when your work is integrated and follow up with updates. You're welcome and encouraged to contact us any time, especially if you have a question about how to continue participating in Open Source after GCI is over, but even if just to keep in touch. Note that ongoing participation in Open Source is one of the most impressive skills to have on your resumé. Take care, be well, and thank you again!