Yesterday a new version of Jenkins Testopia Plug-in was released. This version includes code to avoid printing null when a value returned from Testopia is null. Instead, it now prints an empty String (i.e.: “”).

It has been included i18n support too, with English, Brazilian Portuguese and Dutch (thanks to Peter Florijn) languages. If you use Testopia Plug-in and would like to contribute translating the plug-in, send a pull request.

Check the latest changes and read more about the plug-in on its Wiki page.

Este é o segundo vídeo da série sobre o desenvolvimento de plug-ins para o Jenkins. Neste vídeo vamos abordar como depurar um plug-in, mais sobre extension points e como substituir o Builder padrão por um Publisher no nosso plug-in.

Bom divertimento :-)

It is not exactly an idea, it is more a requirement for BioUno. A common way of administering Batch tasks in computer clusters is using Batch servers such as PBS. The process to submit a job consist of executing a shell script with special “meta” comments that will tell the PBS about your job priority, CPU’s needed, etc.

Jenkins has an awesome remoting API, that has been reworked since its first version in Hudson (it was part of the core IIRC), and can be used for other things. There is a Wiki page about Monitoring external jobs.

What we would need, is query the PBS server, running qstat + parameters locally in the cluster machine. So the requirements that I see:

• Learn more about the remoting API in Jenkins (see http://kohsuke.org/tag/remoting/ too)
• Rework pbs4java or use a wrapper to an existing C API (I’ve read in the past about one, the Python PBS module is a wrapper for this API too)
• Learn about this technique for monitoring external jobs mentioned in that Wiki page
• Write glue code if needed
• Test with a PBS cluster
• Report the findings (paper?)

Just food for thought :D

Edit: There is a label in Jenkins Wiki with several plug-ins that could be used for reference

I’m working in an Apache Nutch project that involves some new plug-ins and customization in existing parts parts of Nutch, however, after reading Nutch’s code base and learning about its plug-in architecture, I believe someone could use part of Jenkins API to enhance the plug-in API in Nutch.

Nutch uses a similar concept, with the same name as in Jenkins, Extension Points. However, it’s quite hard to create a plug-in project separate from the core project (it uses Ivy and plug-ibs have some dependencies to the core project). And you have to extend certain classes and configure XML files to prepare your plug-in.

Part of this could be automatically done with inheritance + Java annotations. I’ll have a cycle for Open Source in the next days, and will give it a try to see if that really makes sense.

Watch the news for more upcoming slides from JUC SF (Jenkins User Conference San Francisco). You can already check Kohsuke Kawaguchi‘s slides. The link is for the reddit thread, so you can comment there and give karma to @agentdero who posted the link.

http://www.reddit.com/r/jenkinsci/comments/10pyv8/jenkins_state_of_the_union_slides_from_juc_sf_2012/

Another interesting news is that now CloudBees Jenkins can deploy to GoogleAppEngine. I believe that in the near future BuildHive will have integration with other platforms and will be able to build software written in many programming languages too.

http://www.reddit.com/r/jenkinsci/comments/10rsp1/cloudbees_jenkins_can_now_deploy_to_google_app/