Unable to trigger a build (svn repository)

Continua CI Discussion
1

Hi, 
I am trying to set a build trigger to run a new build whenever a change is detected in a branch in the repository. 
The repository structure is rather simple: 
-trunk
-branches
–Product1
—Version1
—Version2
–Product2
—Release1
—Release2

The repository monitoring is done on trunk and branches: 
Default Path: trunk
Branches Path: branches
Branch Pattern: /(Product1|Product2)/

There are two triggers set, one is supposed to detect the changes on trunk, the other one should detect the changes on "branches/Product2/Release1/"
The first triggering is working fine, however the second one is not triggered at all. The branch pattern used for the second trigger is: ^branches/Product2/Release1/*
Looking at c:\ContinuaShare\Rc on the continua server, it seems the changes in product2/release1 branch is detected correctly and the changes are presenting in the server disk. 

Do I miss something? Is the defined pattern correct to trigger the build? 
Any help would be appreciated

2

Hi Mohsen,

Note you will need to untick “Match branch pattern against top-level folders only” otherwise the branch pattern on the repository will match /branches/Product1 and /branches/Product2 but not /branches/Product2/Release1

You probably want to use the branch pattern  /(Product1|Product2)/[^/]+/

This will match:

  • /branches/Product1/Version1
  • /branches/Product1/Version2
  • /branches/Product2/Release1
  • /branches/Product2/Release2

Note also the Subversion branches start with a forward slash so your trigger branch pattern would be:

^/branches/Product2/Release1/
3

Hi Dave,

Thanks for the reply.
Updating the value of branch pattern to /(Product1|Product2)/[^/]+/ results No branches matched error
Updated the trigger branch pattern to be ^/branches/Product2/Release1/ but still committed new changes to this branch did not trigger the build.
“Match branch pattern against top-level folders only” is not ticked

Regards,
Mohsen

4

What version of Continua are you using?

5

There’s an issue with the validation when you have “Match branch pattern against top-level folders only” is not ticked. We fixed this for another user but have not put it out in a official release just yet.

You can download the update here:

Continua CI Server Setup 64 bit v1.5.1.121
Continua CI Agent Setup 64 bit v1.5.1.121

6

Hi Dave,

I updated continua with the build you provided and also changed the value of branch pattern to /(Product1|Product2)/[^/]+/
This time it didnt display any error, however the triggering still is not working with committing new changes to /branches/Product2/Release1/

-Mohsen

7

I got the trigger also working with updating the trigger pattern branch to: /branches/Product2/Release1/
previously it was set to ^/branches/Product2/Release1/

Thanks for the help
-Mohsen

8

Hi Mohsen,

Good to hear you’ve got it working. I’d add some validation to the trigger branch pattern to deal with this.