Is it possible to handle multiple branches where some jobs should run on each one, without duplicating jobs?

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

Is it possible to handle multiple branches where some jobs should run on each one, without duplicating jobs?

Kent Larsson-3
Hi,

We have multiple branches: trunk, releasebranch1, releasebranch2, ...

We have a couple of jobs we would like to do on all our branches when
something changes in CVS: Checkout, Build a binary using make, Run
phpunit-tests, Run boost-tests and Deploy to an Apache server

Is there a smart way for us to organize these jobs using Hudson so
that we won't have to duplicate all the above jobs for each branch?

And is there some way to automate the creation of jobs for each new
release branch? We do not release often so setting them up manually is
not a huge problem, but it would be neat if we could automate it
somehow.

Best regards,
Kent Larsson

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

Reply | Threaded
Open this post in threaded view
|

Re: Is it possible to handle multiple branches where some jobs should run on each one, without duplicating jobs?

Mark Waite




----- Original Message ----

> From: Kent Larsson <[hidden email]>
> To: [hidden email]
> Sent: Mon, December 7, 2009 1:12:43 PM
> Subject: Is it possible to handle multiple branches where some jobs should run  on each one, without duplicating jobs?
>
> Hi,
>
> We have multiple branches: trunk, releasebranch1, releasebranch2, ...
>
> We have a couple of jobs we would like to do on all our branches when
> something changes in CVS: Checkout, Build a binary using make, Run
> phpunit-tests, Run boost-tests and Deploy to an Apache server
>
> Is there a smart way for us to organize these jobs using Hudson so
> that we won't have to duplicate all the above jobs for each branch?
>
> And is there some way to automate the creation of jobs for each new
> release branch? We do not release often so setting them up manually is
> not a huge problem, but it would be neat if we could automate it
> somehow.

I've liked using the command line interface to create new jobs with
a standard definition.

http://wiki.hudson-ci.org/display/HUDSON/Hudson+CLI

I can provide more details if you're interested in our technique.

Mark Waite

> Best regards,
> Kent Larsson
>
> ---------------------------------------------------------------------
> 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: Is it possible to handle multiple branches where some jobs should run on each one, without duplicating jobs?

Wim Deblauwe
I am also interested in hearing more on how you do that. We want to use the concept of task branches. It would be great to be able to run a hudson build of such a task branch before you merge back to the main branch.

regards,

Wim

2009/12/8 Mark Waite <[hidden email]>




----- Original Message ----
> From: Kent Larsson <[hidden email]>
> To: [hidden email]
> Sent: Mon, December 7, 2009 1:12:43 PM
> Subject: Is it possible to handle multiple branches where some jobs should run  on each one, without duplicating jobs?
>
> Hi,
>
> We have multiple branches: trunk, releasebranch1, releasebranch2, ...
>
> We have a couple of jobs we would like to do on all our branches when
> something changes in CVS: Checkout, Build a binary using make, Run
> phpunit-tests, Run boost-tests and Deploy to an Apache server
>
> Is there a smart way for us to organize these jobs using Hudson so
> that we won't have to duplicate all the above jobs for each branch?
>
> And is there some way to automate the creation of jobs for each new
> release branch? We do not release often so setting them up manually is
> not a huge problem, but it would be neat if we could automate it
> somehow.

I've liked using the command line interface to create new jobs with
a standard definition.

http://wiki.hudson-ci.org/display/HUDSON/Hudson+CLI

I can provide more details if you're interested in our technique.

Mark Waite

> Best regards,
> Kent Larsson
>
> ---------------------------------------------------------------------
> 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: Is it possible to handle multiple branches where some jobs should run on each one, without duplicating jobs?

Kent Larsson-3
Hi,

Thank you for your answers! I'm also very interested in hearing more
Mr Waite, it sounds like something which could be quite useful.

On Tue, Dec 8, 2009 at 8:28 AM, Wim Deblauwe <[hidden email]> wrote:

> I am also interested in hearing more on how you do that. We want to use the
> concept of task branches. It would be great to be able to run a hudson build
> of such a task branch before you merge back to the main branch.
>
> regards,
>
> Wim
>
> 2009/12/8 Mark Waite <[hidden email]>
>>
>>
>>
>>
>> ----- Original Message ----
>> > From: Kent Larsson <[hidden email]>
>> > To: [hidden email]
>> > Sent: Mon, December 7, 2009 1:12:43 PM5277299318
>> > Subject: Is it possible to handle multiple branches where some jobs
>> > should run  on each one, without duplicating jobs?
>> >
>> > Hi,
>> >
>> > We have multiple branches: trunk, releasebranch1, releasebranch2, ...
>> >
>> > We have a couple of jobs we would like to do on all our branches when
>> > something changes in CVS: Checkout, Build a binary using make, Run
>> > phpunit-tests, Run boost-tests and Deploy to an Apache server
>> >
>> > Is there a smart way for us to organize these jobs using Hudson so
>> > that we won't have to duplicate all the above jobs for each branch?
>> >
>> > And is there some way to automate the creation of jobs for each new5277299318
>> > release branch? We do not release often so setting them up manually is
>> > not a huge problem, but it would be neat if we could automate it
>> > somehow.
>>
>> I've liked using the command line interface to create new jobs with
>> a standard definition.
>>
>> http://wiki.hudson-ci.org/display/HUDSON/Hudson+CLI
>>
>> I can provide more details if you're interested in our technique.
>>
>> Mark Waite
>>
>> > Best regards,
>> > Kent Larsson
>> >
>> > ---------------------------------------------------------------------
>> > 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]
>>
>
>

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

Reply | Threaded
Open this post in threaded view
|

Re: Is it possible to handle multiple branches where some jobs should run on each one, without duplicating jobs?

gschwarz
This post has NOT been accepted by the mailing list yet.
In reply to this post by Kent Larsson-3
Is there already a solution for this?

Creating a branch manually for release branches is not a problem, since there are not many releases anyway, maybe at most one every 2 months.

The objective here would be to create a branch per issue. Since an issue can live for only a few hours or up to a few weeks, it would be nice if Jenkins could create a Jenkins-project-builder for each branch.

Cheers,
Guillermo.