I thought there is a way in continuum as like other CI tools (cruise
control /lunt build) which can be configured to kick off build as soon as
something commited in the source repository..
Thanks,
Raghu
"Morgovsky,
Alexander \(US -
Glen Mills\)" To
<amorgovsky@deloi <continuum-users@maven.apache.org>
tte.com> cc
04/19/2007 04:59 Subject
PM RE: Using XML-RPC client to trigger
builds
Please respond to
continuum-users@m
aven.apache.org
In that case, cannot you set up a schedule which builds every second if
and only if there is a change in SVN?
-----Original Message-----
From: Ben Mills [mailto:ben.mills@intalgent.com]
Sent: Thursday, April 19, 2007 4:43 PM
To: continuum-users@maven.apache.org
Subject: Re: Using XML-RPC client to trigger builds
Just to have it build as soon as a project is updated in SVN and only
then.
On Apr 19, 2007, at 4:35 PM, Morgovsky, Alexander ((US - Glen Mills))
wrote:
> If Continuum can be set up for any schedule, and it detects changes in
> your source code repository, what is the purpose of this XML-RPC
> client
> you need to write?
>
> -----Original Message-----
> From: Ben Mills [mailto:Ben.Mills@intalgent.com]
> Sent: Thursday, April 19, 2007 4:20 PM
> To: continuum-users@maven.apache.org
> Subject: Using XML-RPC client to trigger builds
>
> Greetings,
>
> I need to write an XML-RPC client for Continuum 1.0.3 (linux) and
> call it from a post commit hook (script) in Subversion (linux).
> The purpose is of course to trigger builds via post commit hook.
>
> Before I start, does anyone have any advice about pitfalls or any
> recommendations?
>
> Many thanks,
> Ben
>
>
> This message (including any attachments) contains confidential
> information intended for a specific individual and purpose, and is
> protected by law. If you are not the intended recipient, you
> should delete this message.
>
>
> Any disclosure, copying, or distribution of this message, or the
> taking of any action based on it, is strictly prohibited. [v.E.1]
Disclaimer: This electronic mail and any attachments are confidential and may be privileged.
If you are not the intended recipient, please notify the sender immediately by replying to
this email, and destroy all copies of this email and any attachments. Thank you.
|