Using hutson in mixed platform environments

classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

Using hutson in mixed platform environments

asterix404
All,

I want to set up Hudson in our Mac and Windows environment. These are platform specific builds, so the Mac projects should only build on the Mac build computers and the Windows projects should only build on the Windows build computers. The projects are separate however I wasn't sure how the master/slave relationship for distributed builds worked in this case or which project type I should actually use. If I start having a Master/Slave setup, can I make sure that when I build the Windows project that they don't use the Mac computers to build with? I am not necessarily wanting to pin a project to a single build server however I do want to exclude servers from being used.

Can I do this?
Reply | Threaded
Open this post in threaded view
|

Re: Using hutson in mixed platform environments

Les Mikesell
On 7/28/2010 3:56 PM, asterix404 wrote:

>
> All,
>
> I want to set up Hudson in our Mac and Windows environment. These are
> platform specific builds, so the Mac projects should only build on the Mac
> build computers and the Windows projects should only build on the Windows
> build computers. The projects are separate however I wasn't sure how the
> master/slave relationship for distributed builds worked in this case or
> which project type I should actually use. If I start having a Master/Slave
> setup, can I make sure that when I build the Windows project that they don't
> use the Mac computers to build with? I am not necessarily wanting to pin a
> project to a single build server however I do want to exclude servers from
> being used.

Use labels to identify each type of build you might want.  Add the label
to each node capable of doing that build type, and tie the jobs to the
label.  It's a good idea to do this from the start even if you only have
one build type so you don't have surprises when you add nodes for
different builds.

--
   Les Mikesell
    [hidden email]


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

RE: Using hutson in mixed platform environments

asterix404

Thanks!

 

How do I do that?

 

From: Les Mikesell [via Hudson] [mailto:[hidden email]]
Sent: Wednesday, July 28, 2010 5:08 PM
To: Ben Holland
Subject: Re: Using hutson in mixed platform environments

 

On 7/28/2010 3:56 PM, asterix404 wrote:


>
> All,
>
> I want to set up Hudson in our Mac and Windows environment. These are
> platform specific builds, so the Mac projects should only build on the Mac
> build computers and the Windows projects should only build on the Windows
> build computers. The projects are separate however I wasn't sure how the
> master/slave relationship for distributed builds worked in this case or
> which project type I should actually use. If I start having a Master/Slave
> setup, can I make sure that when I build the Windows project that they don't
> use the Mac computers to build with? I am not necessarily wanting to pin a
> project to a single build server however I do want to exclude servers from
> being used.


Use labels to identify each type of build you might want.  Add the label
to each node capable of doing that build type, and tie the jobs to the
label.  It's a good idea to do this from the start even if you only have
one build type so you don't have surprises when you add nodes for
different builds.

--
   Les Mikesell
    [hidden email]


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]



View message @ http://hudson.361315.n4.nabble.com/Using-hutson-in-mixed-platform-environments-tp2305598p2305617.html
To unsubscribe from Using hutson in mixed platform environments, click here.

 

Reply | Threaded
Open this post in threaded view
|

Re: Using hutson in mixed platform environments

Alex Barna
In reply to this post by asterix404
Assign 'label' to these machines and tie the platform-specific jobs to
these 'labels'.

Alex.

2010/7/28 asterix404 <[hidden email]>:

>
> All,
>
> I want to set up Hudson in our Mac and Windows environment. These are
> platform specific builds, so the Mac projects should only build on the Mac
> build computers and the Windows projects should only build on the Windows
> build computers. The projects are separate however I wasn't sure how the
> master/slave relationship for distributed builds worked in this case or
> which project type I should actually use. If I start having a Master/Slave
> setup, can I make sure that when I build the Windows project that they don't
> use the Mac computers to build with? I am not necessarily wanting to pin a
> project to a single build server however I do want to exclude servers from
> being used.
>
> Can I do this?
>
> --
> View this message in context: http://hudson.361315.n4.nabble.com/Using-hutson-in-mixed-platform-environments-tp2305598p2305598.html
> Sent from the Hudson users mailing list archive at Nabble.com.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Using hutson in mixed platform environments

Les Mikesell
In reply to this post by asterix404
On 7/28/2010 4:11 PM, asterix404 wrote:
> Thanks!
>
> How do I do that?
>

Manage Hudson/Manage Nodes/Tools Icon (configure) at right of each node.
  Fill in the 'Labels' box with one or more names of build types it can
do.  Then when configuring a job you can pick the label/group if you
check the 'Tie this project to a node' box.

--
   Les Mikesell
    [hidden email]


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]