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.
Please sign in to leave a comment.
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
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.
Could you please post corresponding teamcity-server.log and teamcity-vcs.log
And what version and platform do you use?
Michael
TeamCity 6.0.2 on Windows Server 2008 R2.
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.