pre-checkout steps

 Hello All,

before checkout, I need to have some pre checkout steps.
Is this possible with TeamCity?

My specific case:
My TC configuration (conf0) is a running an application (app0) which runs another app (app1).
For some reason, closing app1 is not stable. If app1 is up, app1 locks some files and I cannot do a checkout.

So I have created another configuration (conf1), which kills app1, and a dependency.
This works out okay, but has the drawback that scheduling is now too flexible...
Consider following scenario:
(1) I want to run conf0 multiple times and I have multiple agents.
(2) The agents are quite busy right now apart from one 
(3) So conf1 will run on this single agent multiple times
(4) conf0 is now stuck to this single agent and even if the other agents are now available, I cannot use them.

This scenario happens quite often in my case and is a real issue.

 

Do you have an idea?

0
1 comment

Hi Marcus,

In this scenario there are several possibilities:
-You can make the dependency run on the same agent and mark it as "Always run a new build", so that it doesn't reuse suitable builds. That way, conf1 should always be run before conf0 and in the same agent, accomplishing their task. If your scenario still impedes this, then you can go on with the next option

-You can select "Do not checkout files automatically", then set as your first steps of conf0 the steps you normally would take on conf1, afterwards add a command line script where you checkout the files manually, then have the usual steps from conf0. This is less comfortable, but much more flexible in that regard.

We have this request to include this as a default feature, please watch and vote: https://youtrack.jetbrains.com/issue/TW-14646

0

Please sign in to leave a comment.