TC 10 - Setting a parameter for latest build with tag doesn't work
Completed
Dear Dev Team,
I am currently having a problem after upgrading TC to 10, (from 8), I used a parameter for tag name "build.test.tag", set "patchtest" as its value, and on the job dependenies I created an artifacts source, using "Latest build with tag: %build.test.tag%", and pinned the dependency job, tagged it "patchtest", run the job, it failed to resolve the artifact.
The same process we used while running TC 8. Looking forward to hear from you.
Thanks,
Daniel
Please sign in to leave a comment.
Hello Daniel,
Do you have %build.test.tag% parameter defined in the dependencies? Please attach the whole error reported in UI.
Hi Alina,
This is the full error, but I made it work today, to change the tag from [patchTestFrom] to [patchtestfrom].
Hello Daniel,
Thank you for the update. Did the same setup work before? What tag is set inUE4:GunjackUltimate :: PSVR DEV :: Cook :: COOK Shipping build configuration: [patchTestFrom] or [patchtestfrom]?
it had both, and it worked while I was using TC 8.0, after upgrading to 10, it didn't work, but I am now using all lowercase, works fine, I am thinking i did something wrong at that moment, but I haven't got a chance to test the very beginning case,i.e using uppercase and lowercase, so far its not a problem for me, and very much thanks to you for helping me.
I am running into a similar problem. I sometimes get an error that seems to be related to the build configurations ability to evaluate a tag that is retrieved via a parameter. Example:
Lets say I have a build configuration name BuildContaingArtifact, and each build is tagged with the agent name the build ran on and a version. So build has two tags that look like 'ABC-123' for the build name and 'v2.0.1' for the version.
Now lets say I have a configuration called RunTests who has an artifact dependency on BuildContaingArtifact and the 'Latest finished build with specified tag' is selected and %teamcity.agent.name% is the Build Tag.
This used to work great, but I recently started doing two things differently: 1) Those tags are added via the rest API. 2) I used to only have one tag, the agent name. The version tag is new.
Now sometimes when RunTests gets triggered, I get an error that looks like...: Failed to resolve artifacts from <BuildContaingArtifact, latest build with tag: 'abc-123'>
Based on that error it seems as though %teamcity.agent.name% got converted to lowercase and it can't find the tag 'ABC-123', or maybe it got confused w/ that build having two tags instead of one now. I'm not sure
If I manually run RunTests again, the problem sometimes will go away and it can resolve the artifact build. I'm still in the middle of seeing how this plays out when I'm not manually triggering different things, but I ran into this before a few month ago and finally stumbled across this post that seemed related. Looks like I could play w/ also tagging it w/ a lower cased agent name, but I still wanted to bring this up as an issue.
I'm on version 2017.1.5