New SGE Cloud plugin

[John McGehee]

I have developed a Jenkins plugin that runs jobs on Sun Grid Engine (SGE).  We are using it in production at Wave Computing.

I would like to add it as an official Jenkins plugin.  Can you set me up?

John McGenee

Wave Computing

Campbell, CA

[Daniel Beck]

On 07.03.2016, at 18:44, John McGehee <jmcge...@gmail.com> wrote:

> I would like to add it as an official Jenkins plugin. Can you set me up?

Hi John,

follow the instructions on https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins and we'll set you up.

Daniel

[susa...@gmail.com]

Nice, this could be very useful to us! One question though: is there anyway we can change/affect the command line parameters to qsub?
* We make extensive use of complex variables to select what queues and servers to use. For instance, instead of "-q jenkins.q", we might use "-l jenkinsq,arch=lx24-amd64,OS=RHEL6.6" to select queue, architecture and operating system.
* The default shell at my company is tcsh (don't ask...), so -S /bin/bash is not always appropriate.
* Some users don't want to inherit the environment (-V).

Command line options will not be overridden by #$ in our jobs. Do you have any suggested solution for us? Alternatively, how to we post a feature request? :)

/Susanne Lindgren

[Oleg Nenashev]

Yes, it would be great to see this plugin merged and released.

среда, 9 марта 2016 г., 12:54:24 UTC+3 пользователь susa...@gmail.com написал:

[Jesse Glick]

On Mon, Mar 7, 2016 at 12:44 PM, John McGehee <jmcge...@gmail.com> wrote:
> I have developed a Jenkins plugin that runs jobs on Sun Grid Engine (SGE).

As an aside (not meaning to derail the hosting request!): it might be
valuable to have a corresponding Pipeline step to submit the batch job
and await its completion¹, ideally streaming logs if the engine makes
that possible. After all, it is silly to have a freestyle project
which allocates and locks an executor on some node—intended to signify
that it is *using* that computer for a build—only to make an API call
to a grid engine and then go to sleep for hours. In a Pipeline script,
you can allocate an executor with the `node {}` block step, but you
can also run steps outside of such a block without necessarily
consuming any resources. Furthermore, Jenkins can be restarted while
that Pipeline build is in the middle of an asynchronous step, without
interrupting the Jenkins build or forcing it to be treated as a
failure; it will just resume waiting for the grid engine to finish.


¹Reference: https://github.com/jenkinsci/workflow-plugin/blob/master/step-api/README.md#creating-an-asynchronous-step