Hi Shankar, Just my 0.02 cents here. We are using Jenkins to trigger jobs to MPI and PBS clusters. It will trigger more than one job in your cluster if your job is submitted more than once in Jenkins, just like any other job :-)
What we are doing now, is reading code and looking for a way to include a PBS/MPI/LSF/etc node as executor. So after configuring the plug-in, a PBS slave will appear as an executor in Jenkins like a computer in a cloud infra. And if you submit a job to this executor (a PBS slave) it will query the PBS server to verify if it's free or not (then we can try different approaches, like submitting to another cluster, waiting for a free place in the PBS queue or send it anyway and delegate to the pbs_sched). We are also interested in comparing the scheduler in Jenkins comparing with the default scheduler in Torque PBS (a simple FIFO) and how Torque PBS would behave using Jenkins scheduler (maybe we could turn a Jenkins slave into a PBS slave like the Hadoop Plug-in does, that would be very interesting for computer facilities running PBS torque). The name of our project is BioUno (http://www.biouno.org) and it was presented two weeks ago at ISMB/BOSC conference. With BioUno you can create biology/bioinformatics workflows (mainly with plug-ins) and manage computer facilities (clusters, tools, etc) using Jenkins (and other CI tools in the future ;-). Although Jenkins primary functionality is CI, IMHO, it can be used as a function (like in mathematics or functional programming) in other scenarios and its slaves can be used as general-purpose computing grid.Another idea for using Jenkins as function would be automate a house, with jHome + Arduino (here we could use its scheduler for great use, like to prepare coffee at 6AM :-). I don't have details about your case, but I believe you could try and decide whether it is a good idea to use Jenkins or not. Hope that helps, keep us posted about your progress. Bruno P. Kinoshita http://kinoshita.eti.br http://tupilabs.com >________________________________ > From: shankar krishnan <[email protected]> >To: [email protected] >Sent: Thursday, 26 July 2012 1:36 AM >Subject: Thoughts on Jenkins being used in production environment as a >scheduler > > >We are thinking of using Jenkins scheduling in a production environment. >The following are the points raised by the team as on now. >1. the behaviour of jenkins in a clustered environment >2. will it send multiple triggers to one scheduled job > and other similar issues .. >since the core functionality of jenkins is a continuous integration tool in >development, will it be a viable tool to be used in a production environment >as a scheduler. >Any thoughts or suggestion in this regard will be helpful. >Thanks > > >
