Hi Jesse,

I will probably read the FlyweightTask javadoc&src and will experiment with it.

But that special project type could work too. Any chance to see an Open Source 
version of it this year? :-) 

Thanks!

Bruno


>________________________________
> From: Jesse Glick <[email protected]>
>To: [email protected] 
>Sent: Thursday, June 12, 2014 10:59 AM
>Subject: Re: Jenkins plugin for HPC job systems
> 
>
>On Wed, Jun 11, 2014 at 8:29 PM, 'Bruno P. Kinoshita' via Jenkins
>Developers <[email protected]> wrote:
>> I thought about re-using the monitor-external-job plug-in
>
>It makes for pretty weak integration since it does not let Jenkins
>*initiate* the build. Cf.
>
>http://developer-blog.cloudbees.com/2014/03/support-for-long-running-builds-in.html
>
>> Any advice on how to add items created in the cluster to the build queue in 
>> Jenkins?
>
>I guess you could create a dummy FlyweightTask (tied to the master
>label) whose Executable does nothing but sleep, and schedule it when
>the cluster item is created, but have it claim to be “blocked” (with a
>new cause you define) until the cluster actually starts running it.
>
>I am not sure if that is really intuitive, or if you would better
>define a new Widget showing cluster status in a specialized manner.
>
>James Hetherington wrote:
>> I don't think I understand the durable-task solution, as to me that sounds 
>> like one would not be able to move existing freestyle jobs
>> back and forth between conventional nodes and batch system nodes
>
>Correct; freestyle projects are incapable of surviving Jenkins
>restarts, and I do not think that can be changed. Thus in Jenkins
>Enterprise we added a new project type superficially similar to
>freestyle but using durable-task-plugin for the main build step and
>which does survive restarts. Analogously, workflow builds (using a
>very different UI) can survive restarts and can also use
>durable-task-plugin to manage running your external build process
>during this time.
>
>
>-- 
>You received this message because you are subscribed to the Google Groups 
>"Jenkins Developers" group.
>To unsubscribe from this group and stop receiving emails from it, send an 
>email to [email protected].
>For more options, visit https://groups.google.com/d/optout.
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to