Snapshot Dependencies. Not expected behavior

hi,
I use snapshot dependencies for build in which need to lock some agent before start build. So I have some build configuration called "lock" , and build called "run1" which has snapshot dependency on lock configuration. It's works great. Also I have build configuration called "run2" which has snapshot dependency on "lock" too. It's works great too . But there are some problem when I run cofiguration called "runAll" which has snapshot dependency on run1 and run2. I expected that build Queue  will looks like that :

  • lock
  • run1
  • lock
  • run2
  • runAll

But it's looks like that:
  • lock
  • run1
  • run2
  • runAll


p.s. snapshot dependency on lock configuret with option "allways run new build"

3 comments

Oleksiy,

What you describe seems to an intended case for snapshot dependencies. e.g. if "lock" is compiling build and "run" is a testing build, then typically double compilation is not an expected behaviour.

It seems what you are trying to achive is a bit different. Can you describe what "lock" build is doing and why do you need such setup in the first place so that we can propose some another approach (if available)?

0

thanks I undrestent it all. But when I set option "allways run new build" I expect that build will run every time. However it's not critical, I just copy lock cofiguration and actualy run1 and run2 has different snapshot dependency now.
I need this because I have build which use 2 agent at time, so I want change configuration  of some agent and wait when that agent will be free before start "run" configuration. Actualy I use "lock" cofigure to wailt for agent idle. So I need to wait each time before "run" configure will start.
But how a said abrove it's not critical issue, because I can just copy lock configuration

0

Oleksiy,

"allways run new build" works on per-chain basis, not per-build... We can probably improve the naming, but I am not yet sure how.

0

Please sign in to leave a comment.