Help: TC 7.0.3 - A simple snapshot dependency configuration does not work for me

Hi,

I'm trying to configure a deployment pipeline on a teamcity 7.0.3. Starting with two simple build configuration "build 1" as a  replacement for the commit stage and "build 2" as a  replacement for the component tests.
In the build 2 configuration I'm adding the "build 1" configuration as the snapshot dependency. No build builder trigger. No cvs root.
The build 1 has a vcs root and and the vcs build trigger. The vcs build trigger starts the build 1. After the build is finished nothing further happens. Build 2 will not start. Yet something must be configured?

Thanks for a hint.
Torsten

9 comments
Comment actions Permalink

-- Sorry, this responce was intended for http://devnet.jetbrains.net/thread/437472 --

0
Comment actions Permalink

Hi,

It's not an issue. For the "build 2" I must(!) configure a vcs trigger with checked "Trigger on changes in snapshot dependencies". That's not what I expected. But so it works.

But the following will be definitely  an issue: configure on build 2 the vcs trigger addtional with a trigger rule, build 1 will never trigger the build 2. The trigger rule is well configured: when changes match this trigger rule, build 2 and build 1 are queued in the build queue. But changes on build 1 vcs will only trigger the build 1. After build 1 has finished, nothing else happens.

Greetings
Torsten

0
Comment actions Permalink

Torsten,

If "build 2" snapshot depends on "build 1" then build 2 will trigger build 1 not vice versa. This dependency means that any build of "build 2" has instance of "build 1" that was started on same versions of sources.

You can find more information here: http://confluence.jetbrains.net/display/TCD7/Dependent+Build#DependentBuild-SnapshotDependency

0
Comment actions Permalink

the two builds are configured on the same vcs root. For the two builds a vcs build trigger is configured. So it is possible that teamcity will trigger the second build. Thanks to the the build chain, build 1 will be started before build 2.
But this is not my problem. My problem is with configure in the vcs trigger dialog trigger rules for build 2, for example, a restriction on build runner modules (maven modules) . In build 1 the build runner modules  are exclude (!only via vcs trigger rules).

Torsten

0
Comment actions Permalink

Sorry, I do not quite understand the issue with vcs trigger rules.

Could you please describe the desired behaviour and current behaviour?

0
Comment actions Permalink

At the moment the build chain stop after the build 1 finished, if I have configured a trigger rules in the vcs build trigger of build 2. Removing this vcs trigger rules, all works fine.

ich
Pronomen: ich
0
Comment actions Permalink

I see. Please, attach screenshots of "build 1" and "build 2" vcs trigger configuration pages and screenshot of dependencies configuration page of "build 2"

0
Comment actions Permalink

Here are the screenshots.

Greetings
Torsten



Attachment(s):
snapshot-dependency.png
vcs-tigger-build2.png
vcs-tigger-build1.png
0
Comment actions Permalink

Torsten,

Pending changes from snapshot dependencies are also filtered by vcs trigger rules. Unfortunately, TeamCity only uses build2 vcs trigger rules. So changes in /event1-1/** are ignored according to  [-:.  +:/event1-2/**] pattern. Please watch/vote for this issue: http://youtrack.jetbrains.com/issue/TW-11845

As a workaround, you may want to add third rule +:/event1-1/** to build2 vcs trigger rules.http://youtrack.jetbrains.com/issue/TW-11845

0

Please sign in to leave a comment.