We have a workflow which includes dynamicaly created projects (via rest apis) that requires identical build configurations.
All project have their own git repositories.
Since the build configurations one could create with teamcity is limited and subject to payment,
and we may end up with hundreds of projects since they are dynamically created,
approach we choose to go is, just one configuration with multiple vcs roots.
though, albeit configurations are identical, paths they are operating on supposed to change for each vcs root.
And in my build step, which is a command line script, I need to know name of the vcs root that triggered the build,
so that I can move and copy files accordingly.
I looked at checkout rules and tried to give each vcs root a different checkout directory,
but this did not help me achieve the behaviour I was looking for.
I can simulate this behavior with creating a new teamcity project for each of my projects,
and access env.teamcity_project_name variable in my build step. but then again this is subject to payment.
I am open to suggestions,
Thanks in advance!