You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@continuum.apache.org by Chris Wall <cw...@bea.com> on 2006/06/08 20:39:37 UTC
Subversion post-commit hook
We'd like to trigger Continuum builds upon developer commits in
Subversion. It sounds like to do so we need to develop an xml-rpc
client.
Has anyone developed a post-commit hook into Continuum from Subversion?
Is there related documentation available?
Thanks.
-Chris
_______________________________________________________________________
Notice: This email message, together with any attachments, may contain
information of BEA Systems, Inc., its subsidiaries and affiliated
entities, that may be confidential, proprietary, copyrighted and/or
legally privileged, and is intended solely for the use of the individual
or entity named in this message. If you are not the intended recipient,
and have received this message in error, please immediately return this
by email and then delete it.
Re: Subversion post-commit hook
Posted by Carlos Sanchez <ca...@apache.org>.
yes
On 6/13/06, Lee Meador <le...@leemeador.com> wrote:
> Do I remember right that you can build a tagged version?
>
> On 6/13/06, Emmanuel Venisse <em...@venisse.net> wrote:
> >
> > No, it isn't possible to build a particular revision and I don't see the
> > interest to do it if the
> > code in subversion isn't the latest.
> >
> > Emmanuel
> >
> > Lee Meador a écrit :
> > > To make it work the way I hear you wanting, it looks like you need
> > > something
> > > that notices the changed Subverions revision number and knows the last
> > > revision number that continuum built. Then it causes Continuum to build
> > the
> > > version after the last one built and repeats builds after that of each
> > > subversion version number up to the current one.
> > >
> > > I'm not sure if you can tell Continuum to build a particular Subversion
> > > version number.
> > >
> > > I'm not sure what would happen if a lot of little changes get made all
> > at
> > > once. There could be quite a backlog of builds to do.
> > >
> > > It would even build a version where the only change was to add a space
> > in a
> > > pom, for example, or other change that wouldn't effect the build outcome
> > at
> > > all. Of course, all you would lose is the time.
> > >
> > > -- Lee
> > >
> > > On 6/13/06, Carlos Sanchez <ca...@apache.org> wrote:
> > >>
> > >> On 6/13/06, Baron Reznik <Ba...@fastmobile.com> wrote:
> > >> > On Fri, 2006-06-09 at 18:28 +0200, Carlos Sanchez wrote:
> > >> > > On 6/8/06, Baron.Reznik@fastmobile.com <Baron.Reznik@fastmobile.com
> > >
> > >> wrote:
> > >> > > > I know I'd find this useful as well, for several reasons:
> > >> > > > -If you simply let continuum build every 5 mins, there could
> > >> potentially be more than 1 commit during that time, and you would be
> > >> building multiple revisions worth of changes. Ideally, you would want
> > to
> > >> build once/revision so if the build breaks, you know which commit
> > >> broke it.
> > >> > >
> > >> > >
> > >> > > You are not considering here the time that it takes to build the
> > >> project.
> > >> > > a commits
> > >> > > continuum starts building
> > >> > > b commits
> > >> > > continuum can't start building, busy
> > >> > > c commits
> > >> > > continuum can't start building, busy
> > >> > > continuum finishes building
> > >> > > continuum starts building b and c changes
> > >> > >
> > >> > >
> > >> >
> > >> > ^^^ That's exactly what I'm talking about. Sometimes it will build 1
> > >> > revision, and other times 2 or more revisions could be mixed into one
> > >> > build. I'd like to avoid that.
> > >> >
> > >>
> > >> You can't avoid this with a post commit hook
> > >>
> > >> > >
> > >> > > > -The continuum server would not be making as many hits to the svn
> > >> server. If you're building dozens and dozens of projects, this adds up
> > >> when
> > >> it's once every 5 mins.
> > >> > >
> > >> > > I don't realy know what is the overhead of getting the revision
> > >> number
> > >> > > to check for changes but shouldn't be heavy at all
> > >> > >
> > >> >
> > >> > I don't know how you verify this, but I got the impression that
> > >> > continuum was performing a 'svn update' (for subversion, anyways),
> > >> > which, could be rather heavy depending on how your repository is laid
> > >> > out. I'm not sure offhand if subversion provides a more efficient way
> > >> > though.
> > >> >
> > >>
> > >> svn info gives you the local revision
> > >> svn info URL gives you the remote one
> > >>
> > >> conitnuum may be improved to use this instead of a checkout if it does
> > >> not currently
> > >>
> > >> > > >
> > >> > > > If you got rather fancy, it would sure be nice to have the commit
> > >> check if there were new projects added, and automagically add them to
> > >> continuum as well.
> > >> > > >
> > >> > > >
> > >> > > > -----Original Message-----
> > >> > > > From: carlossg@gmail.com on behalf of Carlos Sanchez
> > >> > > > Sent: Thu 6/8/2006 1:54 PM
> > >> > > > To: continuum-users@maven.apache.org
> > >> > > > Subject: Re: Subversion post-commit hook
> > >> > > >
> > >> > > > why do you need that, setting a short period like 5 min is not
> > >> enough?
> > >> > > >
> > >> > > > On 6/8/06, Chris Wall <cw...@bea.com> wrote:
> > >> > > > > We'd like to trigger Continuum builds upon developer commits in
> > >> > > > > Subversion. It sounds like to do so we need to develop an
> > >> xml-rpc
> > >> > > > > client.
> > >> > > > >
> > >> > > > > Has anyone developed a post-commit hook into Continuum from
> > >> Subversion?
> > >> > > > > Is there related documentation available?
> > >> > > > >
> > >> > > > > Thanks.
> > >> > > > >
> > >> > > > > -Chris
> > >> > > > >
> > >> > > > >
> > >> > > > >
> > >> _______________________________________________________________________
> > >> > > > > Notice: This email message, together with any attachments, may
> > >> contain
> > >> > > > > information of BEA Systems, Inc., its
> > >> subsidiaries and affiliated
> > >> > > > > entities, that may be
> > >> confidential, proprietary, copyrighted and/or
> > >> > > > > legally privileged, and is intended solely for the use of the
> > >> individual
> > >> > > > > or entity named in this message. If you are not the intended
> > >> recipient,
> > >> > > > > and have received this message in error, please immediately
> > >> return
> > >> this
> > >> > > > > by email and then delete it.
> > >> > > > >
> > >> > > > >
> > >> > > >
> > >> > > >
> > >> > > > --
> > >> > > > I could give you my word as a Spaniard.
> > >> > > > No good. I've known too many Spaniards.
> > >> > > > -- The Princess Bride
> > >> > > >
> > >> > > >
> > >> > >
> > >> > >
> > >> >
> > >>
> > >>
> > >> --
> > >> I could give you my word as a Spaniard.
> > >> No good. I've known too many Spaniards.
> > >> -- The Princess Bride
> > >>
> > >
> > >
> > >
> >
> >
>
>
> --
> -- Lee Meador
> Sent from gmail. My real email address is lee@leemeador.com
>
>
--
I could give you my word as a Spaniard.
No good. I've known too many Spaniards.
-- The Princess Bride
Re: Subversion post-commit hook
Posted by Lee Meador <le...@leemeador.com>.
Do I remember right that you can build a tagged version?
On 6/13/06, Emmanuel Venisse <em...@venisse.net> wrote:
>
> No, it isn't possible to build a particular revision and I don't see the
> interest to do it if the
> code in subversion isn't the latest.
>
> Emmanuel
>
> Lee Meador a écrit :
> > To make it work the way I hear you wanting, it looks like you need
> > something
> > that notices the changed Subverions revision number and knows the last
> > revision number that continuum built. Then it causes Continuum to build
> the
> > version after the last one built and repeats builds after that of each
> > subversion version number up to the current one.
> >
> > I'm not sure if you can tell Continuum to build a particular Subversion
> > version number.
> >
> > I'm not sure what would happen if a lot of little changes get made all
> at
> > once. There could be quite a backlog of builds to do.
> >
> > It would even build a version where the only change was to add a space
> in a
> > pom, for example, or other change that wouldn't effect the build outcome
> at
> > all. Of course, all you would lose is the time.
> >
> > -- Lee
> >
> > On 6/13/06, Carlos Sanchez <ca...@apache.org> wrote:
> >>
> >> On 6/13/06, Baron Reznik <Ba...@fastmobile.com> wrote:
> >> > On Fri, 2006-06-09 at 18:28 +0200, Carlos Sanchez wrote:
> >> > > On 6/8/06, Baron.Reznik@fastmobile.com <Baron.Reznik@fastmobile.com
> >
> >> wrote:
> >> > > > I know I'd find this useful as well, for several reasons:
> >> > > > -If you simply let continuum build every 5 mins, there could
> >> potentially be more than 1 commit during that time, and you would be
> >> building multiple revisions worth of changes. Ideally, you would want
> to
> >> build once/revision so if the build breaks, you know which commit
> >> broke it.
> >> > >
> >> > >
> >> > > You are not considering here the time that it takes to build the
> >> project.
> >> > > a commits
> >> > > continuum starts building
> >> > > b commits
> >> > > continuum can't start building, busy
> >> > > c commits
> >> > > continuum can't start building, busy
> >> > > continuum finishes building
> >> > > continuum starts building b and c changes
> >> > >
> >> > >
> >> >
> >> > ^^^ That's exactly what I'm talking about. Sometimes it will build 1
> >> > revision, and other times 2 or more revisions could be mixed into one
> >> > build. I'd like to avoid that.
> >> >
> >>
> >> You can't avoid this with a post commit hook
> >>
> >> > >
> >> > > > -The continuum server would not be making as many hits to the svn
> >> server. If you're building dozens and dozens of projects, this adds up
> >> when
> >> it's once every 5 mins.
> >> > >
> >> > > I don't realy know what is the overhead of getting the revision
> >> number
> >> > > to check for changes but shouldn't be heavy at all
> >> > >
> >> >
> >> > I don't know how you verify this, but I got the impression that
> >> > continuum was performing a 'svn update' (for subversion, anyways),
> >> > which, could be rather heavy depending on how your repository is laid
> >> > out. I'm not sure offhand if subversion provides a more efficient way
> >> > though.
> >> >
> >>
> >> svn info gives you the local revision
> >> svn info URL gives you the remote one
> >>
> >> conitnuum may be improved to use this instead of a checkout if it does
> >> not currently
> >>
> >> > > >
> >> > > > If you got rather fancy, it would sure be nice to have the commit
> >> check if there were new projects added, and automagically add them to
> >> continuum as well.
> >> > > >
> >> > > >
> >> > > > -----Original Message-----
> >> > > > From: carlossg@gmail.com on behalf of Carlos Sanchez
> >> > > > Sent: Thu 6/8/2006 1:54 PM
> >> > > > To: continuum-users@maven.apache.org
> >> > > > Subject: Re: Subversion post-commit hook
> >> > > >
> >> > > > why do you need that, setting a short period like 5 min is not
> >> enough?
> >> > > >
> >> > > > On 6/8/06, Chris Wall <cw...@bea.com> wrote:
> >> > > > > We'd like to trigger Continuum builds upon developer commits in
> >> > > > > Subversion. It sounds like to do so we need to develop an
> >> xml-rpc
> >> > > > > client.
> >> > > > >
> >> > > > > Has anyone developed a post-commit hook into Continuum from
> >> Subversion?
> >> > > > > Is there related documentation available?
> >> > > > >
> >> > > > > Thanks.
> >> > > > >
> >> > > > > -Chris
> >> > > > >
> >> > > > >
> >> > > > >
> >> _______________________________________________________________________
> >> > > > > Notice: This email message, together with any attachments, may
> >> contain
> >> > > > > information of BEA Systems, Inc., its
> >> subsidiaries and affiliated
> >> > > > > entities, that may be
> >> confidential, proprietary, copyrighted and/or
> >> > > > > legally privileged, and is intended solely for the use of the
> >> individual
> >> > > > > or entity named in this message. If you are not the intended
> >> recipient,
> >> > > > > and have received this message in error, please immediately
> >> return
> >> this
> >> > > > > by email and then delete it.
> >> > > > >
> >> > > > >
> >> > > >
> >> > > >
> >> > > > --
> >> > > > I could give you my word as a Spaniard.
> >> > > > No good. I've known too many Spaniards.
> >> > > > -- The Princess Bride
> >> > > >
> >> > > >
> >> > >
> >> > >
> >> >
> >>
> >>
> >> --
> >> I could give you my word as a Spaniard.
> >> No good. I've known too many Spaniards.
> >> -- The Princess Bride
> >>
> >
> >
> >
>
>
--
-- Lee Meador
Sent from gmail. My real email address is lee@leemeador.com
Re: Subversion post-commit hook
Posted by Emmanuel Venisse <em...@venisse.net>.
No, it isn't possible to build a particular revision and I don't see the interest to do it if the
code in subversion isn't the latest.
Emmanuel
Lee Meador a écrit :
> To make it work the way I hear you wanting, it looks like you need
> something
> that notices the changed Subverions revision number and knows the last
> revision number that continuum built. Then it causes Continuum to build the
> version after the last one built and repeats builds after that of each
> subversion version number up to the current one.
>
> I'm not sure if you can tell Continuum to build a particular Subversion
> version number.
>
> I'm not sure what would happen if a lot of little changes get made all at
> once. There could be quite a backlog of builds to do.
>
> It would even build a version where the only change was to add a space in a
> pom, for example, or other change that wouldn't effect the build outcome at
> all. Of course, all you would lose is the time.
>
> -- Lee
>
> On 6/13/06, Carlos Sanchez <ca...@apache.org> wrote:
>>
>> On 6/13/06, Baron Reznik <Ba...@fastmobile.com> wrote:
>> > On Fri, 2006-06-09 at 18:28 +0200, Carlos Sanchez wrote:
>> > > On 6/8/06, Baron.Reznik@fastmobile.com <Ba...@fastmobile.com>
>> wrote:
>> > > > I know I'd find this useful as well, for several reasons:
>> > > > -If you simply let continuum build every 5 mins, there could
>> potentially be more than 1 commit during that time, and you would be
>> building multiple revisions worth of changes. Ideally, you would want to
>> build once/revision so if the build breaks, you know which commit
>> broke it.
>> > >
>> > >
>> > > You are not considering here the time that it takes to build the
>> project.
>> > > a commits
>> > > continuum starts building
>> > > b commits
>> > > continuum can't start building, busy
>> > > c commits
>> > > continuum can't start building, busy
>> > > continuum finishes building
>> > > continuum starts building b and c changes
>> > >
>> > >
>> >
>> > ^^^ That's exactly what I'm talking about. Sometimes it will build 1
>> > revision, and other times 2 or more revisions could be mixed into one
>> > build. I'd like to avoid that.
>> >
>>
>> You can't avoid this with a post commit hook
>>
>> > >
>> > > > -The continuum server would not be making as many hits to the svn
>> server. If you're building dozens and dozens of projects, this adds up
>> when
>> it's once every 5 mins.
>> > >
>> > > I don't realy know what is the overhead of getting the revision
>> number
>> > > to check for changes but shouldn't be heavy at all
>> > >
>> >
>> > I don't know how you verify this, but I got the impression that
>> > continuum was performing a 'svn update' (for subversion, anyways),
>> > which, could be rather heavy depending on how your repository is laid
>> > out. I'm not sure offhand if subversion provides a more efficient way
>> > though.
>> >
>>
>> svn info gives you the local revision
>> svn info URL gives you the remote one
>>
>> conitnuum may be improved to use this instead of a checkout if it does
>> not currently
>>
>> > > >
>> > > > If you got rather fancy, it would sure be nice to have the commit
>> check if there were new projects added, and automagically add them to
>> continuum as well.
>> > > >
>> > > >
>> > > > -----Original Message-----
>> > > > From: carlossg@gmail.com on behalf of Carlos Sanchez
>> > > > Sent: Thu 6/8/2006 1:54 PM
>> > > > To: continuum-users@maven.apache.org
>> > > > Subject: Re: Subversion post-commit hook
>> > > >
>> > > > why do you need that, setting a short period like 5 min is not
>> enough?
>> > > >
>> > > > On 6/8/06, Chris Wall <cw...@bea.com> wrote:
>> > > > > We'd like to trigger Continuum builds upon developer commits in
>> > > > > Subversion. It sounds like to do so we need to develop an
>> xml-rpc
>> > > > > client.
>> > > > >
>> > > > > Has anyone developed a post-commit hook into Continuum from
>> Subversion?
>> > > > > Is there related documentation available?
>> > > > >
>> > > > > Thanks.
>> > > > >
>> > > > > -Chris
>> > > > >
>> > > > >
>> > > > >
>> _______________________________________________________________________
>> > > > > Notice: This email message, together with any attachments, may
>> contain
>> > > > > information of BEA Systems, Inc., its
>> subsidiaries and affiliated
>> > > > > entities, that may be
>> confidential, proprietary, copyrighted and/or
>> > > > > legally privileged, and is intended solely for the use of the
>> individual
>> > > > > or entity named in this message. If you are not the intended
>> recipient,
>> > > > > and have received this message in error, please immediately
>> return
>> this
>> > > > > by email and then delete it.
>> > > > >
>> > > > >
>> > > >
>> > > >
>> > > > --
>> > > > I could give you my word as a Spaniard.
>> > > > No good. I've known too many Spaniards.
>> > > > -- The Princess Bride
>> > > >
>> > > >
>> > >
>> > >
>> >
>>
>>
>> --
>> I could give you my word as a Spaniard.
>> No good. I've known too many Spaniards.
>> -- The Princess Bride
>>
>
>
>
Re: Subversion post-commit hook
Posted by Lee Meador <le...@leemeador.com>.
To make it work the way I hear you wanting, it looks like you need something
that notices the changed Subverions revision number and knows the last
revision number that continuum built. Then it causes Continuum to build the
version after the last one built and repeats builds after that of each
subversion version number up to the current one.
I'm not sure if you can tell Continuum to build a particular Subversion
version number.
I'm not sure what would happen if a lot of little changes get made all at
once. There could be quite a backlog of builds to do.
It would even build a version where the only change was to add a space in a
pom, for example, or other change that wouldn't effect the build outcome at
all. Of course, all you would lose is the time.
-- Lee
On 6/13/06, Carlos Sanchez <ca...@apache.org> wrote:
>
> On 6/13/06, Baron Reznik <Ba...@fastmobile.com> wrote:
> > On Fri, 2006-06-09 at 18:28 +0200, Carlos Sanchez wrote:
> > > On 6/8/06, Baron.Reznik@fastmobile.com <Ba...@fastmobile.com>
> wrote:
> > > > I know I'd find this useful as well, for several reasons:
> > > > -If you simply let continuum build every 5 mins, there could
> potentially be more than 1 commit during that time, and you would be
> building multiple revisions worth of changes. Ideally, you would want to
> build once/revision so if the build breaks, you know which commit broke it.
> > >
> > >
> > > You are not considering here the time that it takes to build the
> project.
> > > a commits
> > > continuum starts building
> > > b commits
> > > continuum can't start building, busy
> > > c commits
> > > continuum can't start building, busy
> > > continuum finishes building
> > > continuum starts building b and c changes
> > >
> > >
> >
> > ^^^ That's exactly what I'm talking about. Sometimes it will build 1
> > revision, and other times 2 or more revisions could be mixed into one
> > build. I'd like to avoid that.
> >
>
> You can't avoid this with a post commit hook
>
> > >
> > > > -The continuum server would not be making as many hits to the svn
> server. If you're building dozens and dozens of projects, this adds up when
> it's once every 5 mins.
> > >
> > > I don't realy know what is the overhead of getting the revision number
> > > to check for changes but shouldn't be heavy at all
> > >
> >
> > I don't know how you verify this, but I got the impression that
> > continuum was performing a 'svn update' (for subversion, anyways),
> > which, could be rather heavy depending on how your repository is laid
> > out. I'm not sure offhand if subversion provides a more efficient way
> > though.
> >
>
> svn info gives you the local revision
> svn info URL gives you the remote one
>
> conitnuum may be improved to use this instead of a checkout if it does
> not currently
>
> > > >
> > > > If you got rather fancy, it would sure be nice to have the commit
> check if there were new projects added, and automagically add them to
> continuum as well.
> > > >
> > > >
> > > > -----Original Message-----
> > > > From: carlossg@gmail.com on behalf of Carlos Sanchez
> > > > Sent: Thu 6/8/2006 1:54 PM
> > > > To: continuum-users@maven.apache.org
> > > > Subject: Re: Subversion post-commit hook
> > > >
> > > > why do you need that, setting a short period like 5 min is not
> enough?
> > > >
> > > > On 6/8/06, Chris Wall <cw...@bea.com> wrote:
> > > > > We'd like to trigger Continuum builds upon developer commits in
> > > > > Subversion. It sounds like to do so we need to develop an xml-rpc
> > > > > client.
> > > > >
> > > > > Has anyone developed a post-commit hook into Continuum from
> Subversion?
> > > > > Is there related documentation available?
> > > > >
> > > > > Thanks.
> > > > >
> > > > > -Chris
> > > > >
> > > > >
> > > > >
> _______________________________________________________________________
> > > > > Notice: This email message, together with any attachments, may
> contain
> > > > > information of BEA Systems, Inc., its
> subsidiaries and affiliated
> > > > > entities, that may be
> confidential, proprietary, copyrighted and/or
> > > > > legally privileged, and is intended solely for the use of the
> individual
> > > > > or entity named in this message. If you are not the intended
> recipient,
> > > > > and have received this message in error, please immediately return
> this
> > > > > by email and then delete it.
> > > > >
> > > > >
> > > >
> > > >
> > > > --
> > > > I could give you my word as a Spaniard.
> > > > No good. I've known too many Spaniards.
> > > > -- The Princess Bride
> > > >
> > > >
> > >
> > >
> >
>
>
> --
> I could give you my word as a Spaniard.
> No good. I've known too many Spaniards.
> -- The Princess Bride
>
--
-- Lee Meador
Sent from gmail. My real email address is lee@leemeador.com
Re: Subversion post-commit hook
Posted by Carlos Sanchez <ca...@apache.org>.
On 6/13/06, Baron Reznik <Ba...@fastmobile.com> wrote:
> On Fri, 2006-06-09 at 18:28 +0200, Carlos Sanchez wrote:
> > On 6/8/06, Baron.Reznik@fastmobile.com <Ba...@fastmobile.com> wrote:
> > > I know I'd find this useful as well, for several reasons:
> > > -If you simply let continuum build every 5 mins, there could potentially be more than 1 commit during that time, and you would be building multiple revisions worth of changes. Ideally, you would want to build once/revision so if the build breaks, you know which commit broke it.
> >
> >
> > You are not considering here the time that it takes to build the project.
> > a commits
> > continuum starts building
> > b commits
> > continuum can't start building, busy
> > c commits
> > continuum can't start building, busy
> > continuum finishes building
> > continuum starts building b and c changes
> >
> >
>
> ^^^ That's exactly what I'm talking about. Sometimes it will build 1
> revision, and other times 2 or more revisions could be mixed into one
> build. I'd like to avoid that.
>
You can't avoid this with a post commit hook
> >
> > > -The continuum server would not be making as many hits to the svn server. If you're building dozens and dozens of projects, this adds up when it's once every 5 mins.
> >
> > I don't realy know what is the overhead of getting the revision number
> > to check for changes but shouldn't be heavy at all
> >
>
> I don't know how you verify this, but I got the impression that
> continuum was performing a 'svn update' (for subversion, anyways),
> which, could be rather heavy depending on how your repository is laid
> out. I'm not sure offhand if subversion provides a more efficient way
> though.
>
svn info gives you the local revision
svn info URL gives you the remote one
conitnuum may be improved to use this instead of a checkout if it does
not currently
> > >
> > > If you got rather fancy, it would sure be nice to have the commit check if there were new projects added, and automagically add them to continuum as well.
> > >
> > >
> > > -----Original Message-----
> > > From: carlossg@gmail.com on behalf of Carlos Sanchez
> > > Sent: Thu 6/8/2006 1:54 PM
> > > To: continuum-users@maven.apache.org
> > > Subject: Re: Subversion post-commit hook
> > >
> > > why do you need that, setting a short period like 5 min is not enough?
> > >
> > > On 6/8/06, Chris Wall <cw...@bea.com> wrote:
> > > > We'd like to trigger Continuum builds upon developer commits in
> > > > Subversion. It sounds like to do so we need to develop an xml-rpc
> > > > client.
> > > >
> > > > Has anyone developed a post-commit hook into Continuum from Subversion?
> > > > Is there related documentation available?
> > > >
> > > > Thanks.
> > > >
> > > > -Chris
> > > >
> > > >
> > > > _______________________________________________________________________
> > > > Notice: This email message, together with any attachments, may contain
> > > > information of BEA Systems, Inc., its subsidiaries and affiliated
> > > > entities, that may be confidential, proprietary, copyrighted and/or
> > > > legally privileged, and is intended solely for the use of the individual
> > > > or entity named in this message. If you are not the intended recipient,
> > > > and have received this message in error, please immediately return this
> > > > by email and then delete it.
> > > >
> > > >
> > >
> > >
> > > --
> > > I could give you my word as a Spaniard.
> > > No good. I've known too many Spaniards.
> > > -- The Princess Bride
> > >
> > >
> >
> >
>
--
I could give you my word as a Spaniard.
No good. I've known too many Spaniards.
-- The Princess Bride
Re: Subversion post-commit hook
Posted by Baron Reznik <Ba...@fastmobile.com>.
On Fri, 2006-06-09 at 18:28 +0200, Carlos Sanchez wrote:
> On 6/8/06, Baron.Reznik@fastmobile.com <Ba...@fastmobile.com> wrote:
> > I know I'd find this useful as well, for several reasons:
> > -If you simply let continuum build every 5 mins, there could potentially be more than 1 commit during that time, and you would be building multiple revisions worth of changes. Ideally, you would want to build once/revision so if the build breaks, you know which commit broke it.
>
>
> You are not considering here the time that it takes to build the project.
> a commits
> continuum starts building
> b commits
> continuum can't start building, busy
> c commits
> continuum can't start building, busy
> continuum finishes building
> continuum starts building b and c changes
>
>
^^^ That's exactly what I'm talking about. Sometimes it will build 1
revision, and other times 2 or more revisions could be mixed into one
build. I'd like to avoid that.
>
> > -The continuum server would not be making as many hits to the svn server. If you're building dozens and dozens of projects, this adds up when it's once every 5 mins.
>
> I don't realy know what is the overhead of getting the revision number
> to check for changes but shouldn't be heavy at all
>
I don't know how you verify this, but I got the impression that
continuum was performing a 'svn update' (for subversion, anyways),
which, could be rather heavy depending on how your repository is laid
out. I'm not sure offhand if subversion provides a more efficient way
though.
> >
> > If you got rather fancy, it would sure be nice to have the commit check if there were new projects added, and automagically add them to continuum as well.
> >
> >
> > -----Original Message-----
> > From: carlossg@gmail.com on behalf of Carlos Sanchez
> > Sent: Thu 6/8/2006 1:54 PM
> > To: continuum-users@maven.apache.org
> > Subject: Re: Subversion post-commit hook
> >
> > why do you need that, setting a short period like 5 min is not enough?
> >
> > On 6/8/06, Chris Wall <cw...@bea.com> wrote:
> > > We'd like to trigger Continuum builds upon developer commits in
> > > Subversion. It sounds like to do so we need to develop an xml-rpc
> > > client.
> > >
> > > Has anyone developed a post-commit hook into Continuum from Subversion?
> > > Is there related documentation available?
> > >
> > > Thanks.
> > >
> > > -Chris
> > >
> > >
> > > _______________________________________________________________________
> > > Notice: This email message, together with any attachments, may contain
> > > information of BEA Systems, Inc., its subsidiaries and affiliated
> > > entities, that may be confidential, proprietary, copyrighted and/or
> > > legally privileged, and is intended solely for the use of the individual
> > > or entity named in this message. If you are not the intended recipient,
> > > and have received this message in error, please immediately return this
> > > by email and then delete it.
> > >
> > >
> >
> >
> > --
> > I could give you my word as a Spaniard.
> > No good. I've known too many Spaniards.
> > -- The Princess Bride
> >
> >
>
>
Re: Subversion post-commit hook
Posted by Carlos Sanchez <ca...@apache.org>.
On 6/8/06, Baron.Reznik@fastmobile.com <Ba...@fastmobile.com> wrote:
> I know I'd find this useful as well, for several reasons:
> -If you simply let continuum build every 5 mins, there could potentially be more than 1 commit during that time, and you would be building multiple revisions worth of changes. Ideally, you would want to build once/revision so if the build breaks, you know which commit broke it.
You are not considering here the time that it takes to build the project.
a commits
continuum starts building
b commits
continuum can't start building, busy
c commits
continuum can't start building, busy
continuum finishes building
continuum starts building b and c changes
> -The continuum server would not be making as many hits to the svn server. If you're building dozens and dozens of projects, this adds up when it's once every 5 mins.
I don't realy know what is the overhead of getting the revision number
to check for changes but shouldn't be heavy at all
>
> If you got rather fancy, it would sure be nice to have the commit check if there were new projects added, and automagically add them to continuum as well.
>
>
> -----Original Message-----
> From: carlossg@gmail.com on behalf of Carlos Sanchez
> Sent: Thu 6/8/2006 1:54 PM
> To: continuum-users@maven.apache.org
> Subject: Re: Subversion post-commit hook
>
> why do you need that, setting a short period like 5 min is not enough?
>
> On 6/8/06, Chris Wall <cw...@bea.com> wrote:
> > We'd like to trigger Continuum builds upon developer commits in
> > Subversion. It sounds like to do so we need to develop an xml-rpc
> > client.
> >
> > Has anyone developed a post-commit hook into Continuum from Subversion?
> > Is there related documentation available?
> >
> > Thanks.
> >
> > -Chris
> >
> >
> > _______________________________________________________________________
> > Notice: This email message, together with any attachments, may contain
> > information of BEA Systems, Inc., its subsidiaries and affiliated
> > entities, that may be confidential, proprietary, copyrighted and/or
> > legally privileged, and is intended solely for the use of the individual
> > or entity named in this message. If you are not the intended recipient,
> > and have received this message in error, please immediately return this
> > by email and then delete it.
> >
> >
>
>
> --
> I could give you my word as a Spaniard.
> No good. I've known too many Spaniards.
> -- The Princess Bride
>
>
--
I could give you my word as a Spaniard.
No good. I've known too many Spaniards.
-- The Princess Bride
RE: Subversion post-commit hook
Posted by Ba...@fastmobile.com.
I know I'd find this useful as well, for several reasons:
-If you simply let continuum build every 5 mins, there could potentially be more than 1 commit during that time, and you would be building multiple revisions worth of changes. Ideally, you would want to build once/revision so if the build breaks, you know which commit broke it.
-The continuum server would not be making as many hits to the svn server. If you're building dozens and dozens of projects, this adds up when it's once every 5 mins.
If you got rather fancy, it would sure be nice to have the commit check if there were new projects added, and automagically add them to continuum as well.
-----Original Message-----
From: carlossg@gmail.com on behalf of Carlos Sanchez
Sent: Thu 6/8/2006 1:54 PM
To: continuum-users@maven.apache.org
Subject: Re: Subversion post-commit hook
why do you need that, setting a short period like 5 min is not enough?
On 6/8/06, Chris Wall <cw...@bea.com> wrote:
> We'd like to trigger Continuum builds upon developer commits in
> Subversion. It sounds like to do so we need to develop an xml-rpc
> client.
>
> Has anyone developed a post-commit hook into Continuum from Subversion?
> Is there related documentation available?
>
> Thanks.
>
> -Chris
>
>
> _______________________________________________________________________
> Notice: This email message, together with any attachments, may contain
> information of BEA Systems, Inc., its subsidiaries and affiliated
> entities, that may be confidential, proprietary, copyrighted and/or
> legally privileged, and is intended solely for the use of the individual
> or entity named in this message. If you are not the intended recipient,
> and have received this message in error, please immediately return this
> by email and then delete it.
>
>
--
I could give you my word as a Spaniard.
No good. I've known too many Spaniards.
-- The Princess Bride
Re: Subversion post-commit hook
Posted by Carlos Sanchez <ca...@apache.org>.
why do you need that, setting a short period like 5 min is not enough?
On 6/8/06, Chris Wall <cw...@bea.com> wrote:
> We'd like to trigger Continuum builds upon developer commits in
> Subversion. It sounds like to do so we need to develop an xml-rpc
> client.
>
> Has anyone developed a post-commit hook into Continuum from Subversion?
> Is there related documentation available?
>
> Thanks.
>
> -Chris
>
>
> _______________________________________________________________________
> Notice: This email message, together with any attachments, may contain
> information of BEA Systems, Inc., its subsidiaries and affiliated
> entities, that may be confidential, proprietary, copyrighted and/or
> legally privileged, and is intended solely for the use of the individual
> or entity named in this message. If you are not the intended recipient,
> and have received this message in error, please immediately return this
> by email and then delete it.
>
>
--
I could give you my word as a Spaniard.
No good. I've known too many Spaniards.
-- The Princess Bride
Re: Subversion post-commit hook
Posted by Emmanuel Venisse <em...@venisse.net>.
xml-rpc documentation is there : http://maven.apache.org/continuum/guides/mini/guide-xmlrpc-api.html
Emmanuel
Chris Wall a écrit :
> We'd like to trigger Continuum builds upon developer commits in
> Subversion. It sounds like to do so we need to develop an xml-rpc
> client.
>
> Has anyone developed a post-commit hook into Continuum from Subversion?
> Is there related documentation available?
>
> Thanks.
>
> -Chris
>
>
> _______________________________________________________________________
> Notice: This email message, together with any attachments, may contain
> information of BEA Systems, Inc., its subsidiaries and affiliated
> entities, that may be confidential, proprietary, copyrighted and/or
> legally privileged, and is intended solely for the use of the individual
> or entity named in this message. If you are not the intended recipient,
> and have received this message in error, please immediately return this
> by email and then delete it.
>