Quantcast

Multiconfiguration build with different steps?

classic Classic list List threaded Threaded
7 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Multiconfiguration build with different steps?

JR Cary
Hi,

I am trying to use multiconfiguration build with different steps.

On unix, it is a simple script execution.

On windows, I need to do a windows batch command like

   C:\cygwin\bash --login  otherscript.sh


Can I specify the build step by node?

Thx...John Cary
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Multiconfiguration build with different steps?

domi@fortysix.ch
Have a look at the conditional build step plugin [1]
I guess its just a question of how to define the condition - if you find yourself missing a condition, please open a feature request.
/Domi

[1] https://wiki.jenkins-ci.org/display/JENKINS/Conditional+BuildStep+Plugin

On 11.01.2012, at 18:48, John R. Cary wrote:

> Hi,
>
> I am trying to use multiconfiguration build with different steps.
>
> On unix, it is a simple script execution.
>
> On windows, I need to do a windows batch command like
>
>  C:\cygwin\bash --login  otherscript.sh
>
>
> Can I specify the build step by node?
>
> Thx...John Cary

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Multiconfiguration build with different steps?

Les Mikesell
In reply to this post by JR Cary
On Wed, Jan 11, 2012 at 11:48 AM, John R. Cary <[hidden email]> wrote:

> Hi,
>
> I am trying to use multiconfiguration build with different steps.
>
> On unix, it is a simple script execution.
>
> On windows, I need to do a windows batch command like
>
>  C:\cygwin\bash --login  otherscript.sh
>
>
> Can I specify the build step by node?

The Xshell plugin is probably the simplest approach.  It will let you
have a shell script and a batch file with the same name except having
a .bat extension on the batch file, and will execute the one with .bat
on windows nodes.

--
   Les Mikesell
    [hidden email]
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Multiconfiguration build with different steps?

Chris Withers
In reply to this post by domi@fortysix.ch
On 11/01/2012 18:20, domi wrote:
> Have a look at the conditional build step plugin [1]
> I guess its just a question of how to define the condition - if you find yourself missing a condition, please open a feature request.
> /Domi
>
> [1] https://wiki.jenkins-ci.org/display/JENKINS/Conditional+BuildStep+Plugin

You might also consider:

https://wiki.jenkins-ci.com/display/JENKINS/XShell+Plugin

cheers,

Chris

--
Simplistix - Content Management, Batch Processing & Python Consulting
             - http://www.simplistix.co.uk
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

RE: Multiconfiguration build with different steps?

Lars Nordin
You might also consider using python instead of a shell script and then having it figure out if it is on Linux or Windows, etc.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Multiconfiguration build with different steps?

Les Mikesell
On Thu, Jan 12, 2012 at 7:38 AM, Lars Nordin <[hidden email]> wrote:
> You might also consider using python instead of a shell script and then having it figure out if it is on Linux or Windows, etc.

Or the groovy plugin should work for that too.  You might not have
python on the target, but groovy should always run on the slaves.

--
  Les Mikesell
    [hidden email]
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Multiconfiguration build with different steps?

Sami Tikka
Another possibility is to use an ant build step to run a shell script on unix and bat file on windows.

-- Sami

Les Mikesell <[hidden email]> kirjoitti 12.1.2012 kello 16.31:

> On Thu, Jan 12, 2012 at 7:38 AM, Lars Nordin <[hidden email]> wrote:
>> You might also consider using python instead of a shell script and then having it figure out if it is on Linux or Windows, etc.
>
> Or the groovy plugin should work for that too.  You might not have
> python on the target, but groovy should always run on the slaves.
>
> --
>  Les Mikesell
>    [hidden email]
Loading...