TKLPatch for Jenkins (Hudson)

I was ashamed to ask to include hudson but I reaaally wanted to happen! To be honest, I'll start using it this month, that's why I prepared this tklpatch, to give it a ride. I just can't install something without making the patch :P

I tell you how it goes, I'm also waiting for the final openldap appliance for a super-secret project I'm working on mwahahaha...

That's the kind of feedback I was waiting for! Just today I haven't finished deploying my hudson server at home, but yes, reading a bit I found that at least ant should be in there. 

I'll follow your suggestions, right now I'm interested in having support for java, ruby, python and php. 

But I'll try not to include the most used generic plugins as it's important to keep it light and let the final users customize as they see fit.

Thanks for your suggestions!

I am using Hudson on a daily basis. Unfortunately, I have to run it on windoze:(, so cannot be of much help. However, I can offer some observations for what it worth.

Hudson is essentially a build server with Java being the favorite (but by no means the only) target. To do something useful you would want to include some build tools as well as unit testing, logging and documentation tools for every target language.

Examples:
Java: JDK, Ant, Maven, jUnit, javadoc, log4j...
Cpp: gcc, make, CMake, cppUnit, doxygen ...
Python: py.test, nose, sphinx, epydoc...
...

You would also want to install Hudson plugins for version control systems (except SVN and CVS, which are included.)

There is about a million of other plugins, good luck with that.

Jenkins is about to release their first version (latest hudson) and I think we should go with them. I'm also adding new things to the patch, so please wait until I complete a new version this week. My plans for this next release are to:

- Add plugins for the TKL supported scm (git, svn, hg, ?)

- Add ant, rake, gcc, make and openjdk (I haven't decided yet on maven). 

- Add xUnit support for java/php/python/ruby (still need to research what's available)

- Add inithook to secure jenkins on firstboot (best practice)

As you can see in Vyacheslav Rafalskiy's comment, he suggest some other things, but I'll need some help on deciding, as there are lots of plugins there, but my main idea is to support java, php, ruby, and python, but maybe I should include C++ also?. But I agree with him on including at least a build tool, a unit testing library, and a documentation tool for autogenerating docs. I'm not really sure how useful is logging tool? My lack of experience on the subject doesn't help. 

So yes, please wait a bit to see what can be added. 

As for the Python part, both py.test and nose support output in xUnit format.

I outline below the way I configure my environments. You may find it helpful.

# a workaround to avoid using broken version of setuptools (python-setuptools)
apt-get install python-pip  # package manager
pip install distribute      # this will bring the patched version of setuptools

# the rest of packages are installed from PyPI
# from this point both 'easy_install' and 'pip install' will work

easy_install virtualenv # de-facto standard for creating independent development and deployment environments
easy_install nose    # unit test framework
easy_install pytest  # unit test framework
easy_install sphinx  # documentation tool
easy_install epydoc  # API documentation tool