Build trigger filters not working after adding build steps

Yesterday I modified a build config to use multiple build steps. Previously, the build was entirely run by means of a shell script which among other things, ran maven commands. I removed a maven step and added it as the first build step followed by the shell script which runs the rest of the build.

Since making this change, I notice that VCS trigger filters are no longer followed. Changes to a source tests directory should be ignored and not trigger a build. But, since adding the build step, it appears that the trigger exclusion no longer works. I have not made any change to the build config other than adding the new build step.

-Dave

3 comments
Comment actions Permalink

I doubt the VCS trigger problem is somehow related to build steps configuration. This is highly unlikely. Could you please provide your VCS trigger settings and examples of changes which triggered a build, but should not? BTW, what is shown in the Triggered By column on the build results page for such build?

0
Comment actions Permalink

pavel.sher wrote:

I doubt the VCS trigger problem is somehow related to build steps configuration. This is highly unlikely. Could you please provide your VCS trigger settings and examples of changes which triggered a build, but should not? BTW, what is shown in the Triggered By column on the build results page for such build?


It seemed unlikely to me that this was related to multiple builds steps too. But, after it happened 3 times yesterday, I couldn't see any other change that might have caused the problem.

Just to be clear, there is one build config that that has a VCS trigger to build upon svn changes to the trunk in a specific code path except if the changes are in a certain subdir. This filter has been in place for at least 6 months and has always worked fine until the last couple of days.

Answers to your questions:
The VCS trigger settings are:
-:vagabond-tests/**

Change example:
There were 69 modified files in one change that triggered the build.
All the files in this change are under here relative to the root: vagabond-tests/record-replay/
Example file (full path in svn):
/vagabond/trunk/vagabond-parent/vagabond-tests/record-replay/autoCancel/ac001-BR-autoCancel-ten-P/compare.xml

Triggered by:
Triggered by:         Subversion; Vagabond Nightly Deployments :: DEV2 on 08 Mar 11 13:03

This is interesting because it appears that the build was triggered by the check-in (subversion) AND a build that is dependent on this build (Vagabond Nightly Deployments :: DEV2).

The "Vagabond Nightly Deployments :: DEV2" is a continuous integration build that runs whenever there as a change to the svn trunk. It does not have any trigger settings. So, perhaps that is the answer: that the DEV2 build caused the other build to start and it follows its own VCS trigger rules rather than the VCS rules of the build on which it depends.

-Dave

0
Comment actions Permalink

Based on the comment I made above I believe that adding build steps had nothing to do with the build trigger. So, I am marking this question answered.

-Dave

0

Please sign in to leave a comment.