As a workaround possibility, couldn't you fire off code that found out the
modified branches from the commit just made (using the svn command-line
client) and re-run your test rigs if it turns out this is the case?

I don't work for Google btw. :-)

:Darren.

On Wed, Jan 18, 2012 at 22:16, Anton Rieder <[email protected]> wrote:

> Hi,
>
> The project I work for makes heavy use of feature branches and we have
> many developers working in parallel. We also use Jenkins as our build
> server. Currently we poll the 'default' branch for changes every N
> minutes so the unit tests are ran if there is a merge, back into the
> default branch from our feature branches. I'd love to use the Post-
> Commit Web Hook instead of polling, but I did not see the 'branch'
> info in the info sent.
>
> So here's my question:
> Is there, currently, a way to only trigger the hook when there are
> commits to the default branch? Either by parsing additional info about
> what branch was affected by the commit or other means?
>
>
> Cheers,
> Anton
>
> --
> You received this message because you are subscribed to the Google Groups
> "Project Hosting on Google Code" group.
> To post to this group, send email to [email protected].
> To unsubscribe from this group, send email to
> [email protected].
> For more options, visit this group at
> http://groups.google.com/group/google-code-hosting?hl=en.
>
>


-- 
----------------------------------------------------------------------
:Darren :Pearce-Lazard
----------------------------------------------------------------------<http://www.linkedin.com/in/darrenpearce>
Today's dingbat from dingbatman <http://www.dingbatman.com/>:
----------------------------------------------------------------------
<http://www.dingbatman.com>
----------------------------------------------------------------------

-- 
You received this message because you are subscribed to the Google Groups 
"Project Hosting on Google Code" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/google-code-hosting?hl=en.

Reply via email to