Artifact Dependency Configuration Being Ignored?

So I have two projects:

A (library)
B (exe)

B depends on A with:

- Do not run new build if there is a suitable one

- Only use successful builds from suitable ones

As I understand it, if there is an up to date build of A, it shouldn't be rebuilt, but it's building every time B builds, which causes version mismatches between software that share the same library code base.

Am I configuring this wrong?


Edit: Ugh I keep forgetting to change the type of thread to question so I can award points for helping... :( sorry.

0
4 comments

Do the confugurations have separate VCS roots or share the same one?
In last case commiting any chage to exe project will force teamCity ro rebuild library project too.

Michael

0

2 completely seperate roots.

$/ProjectA
$/ProjectB/Version1.0

The changes are being comitted to Project B, but Project A continues to rebuild when project B is built.

Last two builds (1.0.8, 1.0.9) have no changes on Project A, neither were manually triggered.

0

Could you please post corresponding teamcity-server.log and teamcity-vcs.log

And what version and platform do you use?

Michael

0

TeamCity 6.0.2 on Windows Server 2008 R2.


[2011-02-23 13:43:32,239]   INFO - tbrains.buildServer.ACTIVITIES - Build started; name=Project A :: Build Trunk, personal=false, buildId=205
[2011-02-23 13:43:32,239]   INFO - tbrains.buildServer.ACTIVITIES - Configuration removed from queue; name=Project A :: Build Trunk, requestor=William Roush; Project B :: Build Trunk, comment=null, user=null, promotion id=205
[2011-02-23 13:43:32,239]   INFO -   jetbrains.buildServer.SERVER - Flush queue finished, number of builds started: 1
[2011-02-23 13:43:32,254]   INFO -   jetbrains.buildServer.SERVER - Running build saved to DB: Project A :: Build Trunk {id=bt4} # #1.0.9 {build id=205} on agent Local Build Agent 3 triggered by ##userId='1' buildTypeId='bt2'
[2011-02-23 13:43:38,541]   INFO - de.impl.history.DBBuildHistory - Start creating history entry for Project A :: Build Trunk 205, date: 1298486618000
[2011-02-23 13:43:38,541]   INFO - de.impl.history.DBBuildHistory - End creating history entry for Project A :: Build Trunk 205
[2011-02-23 13:43:38,557]   INFO - tbrains.buildServer.ACTIVITIES - Finished 205
[2011-02-23 13:43:38,651]   INFO - tbrains.buildServer.ACTIVITIES - Build started; name=Project B :: Build Trunk, personal=false, buildId=206
[2011-02-23 13:43:38,651]   INFO - tbrains.buildServer.ACTIVITIES - Configuration removed from queue; name=Project B :: Build Trunk, requestor=William Roush, comment=null, user=null, promotion id=206
[2011-02-23 13:43:38,651]   INFO -   jetbrains.buildServer.SERVER - Flush queue finished, number of builds started: 1
[2011-02-23 13:43:38,682]   INFO -   jetbrains.buildServer.SERVER - Running build saved to DB: Project B :: Build Trunk {id=bt2} # #1.0.20 {build id=206} on agent Local Build Agent 2 triggered by ##userId='1'
[2011-02-23 13:43:52,495]   INFO - de.impl.history.DBBuildHistory - Start creating history entry for Project B :: Build Trunk 206, date: 1298486632000
[2011-02-23 13:43:52,495]   INFO - de.impl.history.DBBuildHistory - End creating history entry for Project B :: Build Trunk 206
[2011-02-23 13:43:52,510]   INFO - tbrains.buildServer.ACTIVITIES - Finished 206



[2011-02-23 13:43:32,489]   INFO [rmal executor 5] -      jetbrains.buildServer.VCS - Requesting patch: root=vss: \\vssserver\SourceSafe\srcsafe.ini $/Project A {id=3}, cleanPatch=false, prevVersion=1298486399454, newVersion=1298486603676, buildType=Project A :: Build Trunk {id=bt4}, buildId=205
[2011-02-23 13:43:33,458]   INFO [rmal executor 5] - .vcs.vss.runner.SSPatchBuilder - stdout:
C:\TeamCity\temp\TC-VSS-10421-ss_native>SET SSDIR=\\vssserver\SourceSafe

C:\TeamCity\temp\TC-VSS-10421-ss_native>"C:\Program Files (x86)\Microsoft Visual SourceSafe\ss.exe" Get $/Project A/ -R -Vd2/23/2011;1:43:24p -Y[User],[Pass] -I-Y -W -GF- -GTM -GWR
Getting [Files]


[2011-02-23 13:43:33,458]   INFO [rmal executor 5] - .vcs.vss.runner.SSPatchBuilder - stderr: Folder C:\TeamCity\temp\TC-VSS-10406-ss_native not found, create?(Y/N)Y
Set C:\TeamCity\temp\TC-VSS-10421-ss_native as the default folder for project $/Project A?(Y/N)Y


[2011-02-23 13:43:33,489]   INFO [rmal executor 5] -      jetbrains.buildServer.VCS - Done requesting patch for root vss: \\vssserver\SourceSafe\srcsafe.ini $/Project A {id=3} cleanPatch = false, prevVersion=1298486399454, newVersion=1298486603676, buildId = 205; took 993 msec
[2011-02-23 13:43:34,652]   INFO [p-8080-4 /RPC2 ] -      jetbrains.buildServer.VCS - Patch applied for agent=Local Build Agent 3 {host=127.0.0.1}, buildType=Project A :: Build Trunk {id=bt4}, root=vss: \\vssserver\SourceSafe\srcsafe.ini $/Project A {id=3}, version=1298486603676
[2011-02-23 13:43:39,120]   INFO [rmal executor 9] -      jetbrains.buildServer.VCS - Requesting patch: root=vss: \\vssserver\SourceSafe\srcsafe.ini $/Project B/Project B 1.0 {id=1}, cleanPatch=false, prevVersion=1298486399454, newVersion=1298486603676, buildType=Project B :: Build Trunk {id=bt2}, buildId=206
[2011-02-23 13:43:46,198]   INFO [rmal executor 9] -      jetbrains.buildServer.VCS - Done requesting patch for root vss: \\vssserver\SourceSafe\srcsafe.ini $/Project B/Project B 1.0 {id=1} cleanPatch = false, prevVersion=1298486399454, newVersion=1298486603676, buildId = 206; took 7 sec 68 msec
[2011-02-23 13:43:48,125]   INFO [p-8080-3 /RPC2 ] -      jetbrains.buildServer.VCS - Patch applied for agent=Local Build Agent 2 {host=127.0.0.1}, buildType=Project B :: Build Trunk {id=bt2}, root=vss: \\vssserver\SourceSafe\srcsafe.ini $/Project B/Project B 1.0 {id=1}, version=1298486603676




It's not really a huge issue, I'll go ahead and reconfigure it once we start working on the main library again and make sure I'm not a complete fool and messed this up on my end, but I'll drop this in here for reference anyway. I cropped out "Getting [Files]", it does list the entire project, it most likely is a VSS thing I think, so let me look into that.



Edit:
Checkout Options: [x] Perform full checkout on every build.

Would that be causing it?

Just in case, I unchecked it and re-added the snapshot dependency, I'll check back when I rebuild our main project and confirm if that fixed it.

0

Please sign in to leave a comment.