3 Replies Last post: Mar 21, 2014 7:04 PM by Sergey Pak  
Bryan Dollery Newbie 2 posts since
Mar 20, 2014
Currently Being Moderated

Mar 20, 2014 7:03 PM

TC8.0.3 Finish Build Trigger & SVN Update

We have a five step build process:

 

  1. Build & Unit-Test
  2. Container-Test
  3. Package for deployment
  4. Deploy to functional test environment
  5. Deploy to integration test environment

 

Steps 2 & 3 are triggered by a fiish build trigger on step 1. Step 4 is triggered by a finish build trigger on step 3, and uses the artifacts generated in 3. Step 5 is manual.

 

Steps 1 through 3 are maven builds performed on a clean checkout of the head from subversion. Herein lies the problem. If a developer commits during step 1, then steps 2 and 3 will be run against a different revision than step 1. With really bad timing it is possible for steps 1 through 3 to run on different revisions.

 

Is there a way to carry the revision number from step 1 through the other steps?

Sergey Pak JetBrains 323 posts since
Nov 13, 2013
Currently Being Moderated
Mar 21, 2014 4:47 PM in response to: Bryan Dollery
Re: TC8.0.3 Finish Build Trigger & SVN Update

If you want to use build.number from another build, you should have snapshot dependency (direct or indirect) and use parameter %dep.<Base_CONFname>.build.number%.

Sergey Pak JetBrains 323 posts since
Nov 13, 2013
Currently Being Moderated
Mar 21, 2014 7:05 PM in response to: Bryan Dollery
Re: TC8.0.3 Finish Build Trigger & SVN Update

Actually, I read your first post wrong. What you need is just snapshot dependencies and nothing else http://confluence.jetbrains.com/display/TCD8/Snapshot+Dependencies.

 

And in the artifact dependency you should use "build from the same chain"

More Like This

  • Retrieving data ...