continuum-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ben Mills <ben.mi...@intalgent.com>
Subject Re: Using XML-RPC client to trigger builds
Date Thu, 19 Apr 2007 21:12:30 GMT
First, I'd like to thank you for all your assistance and time today.
And yes, I imagine that would be a lot easier than dealing with the  
client and script.

Even just every 5 min would probably be fine...

So a quartz/CronTrigger for every 5 min would be

0 0/5 * * * ?

is that correct?

On Apr 19, 2007, at 4:58 PM, Morgovsky, Alexander ((US - Glen Mills))  
wrote:

> 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]
>


Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message