Identify which VCS root triggered build?

If I have multipe VCS roots monitoring multiple Git repositories, for shared code project for example, and I want to build and test on changes to any VCS root, is there a way to identify which of the VCS roots changed and triggered the build?

3 comments
Comment actions Permalink

Hi Jeff,

Why do you need to get this information?

0
Comment actions Permalink

Like I mentioned above this is a shared code project with many Git repositories ( VCS roots) and we would like to do some dynamic building, scripting, etc based on the VCS root that triggered the build rather than always post process every repository.  We are looking for efficentcy as many changes are coming in from various sites and developers, and we can't always just add build agents to handle all the changes, this would allow us to same a good deal of time building and testing each change.

0
Comment actions Permalink

Sorry for delay. It is not a good practice to change the logic of the build inside build script. In this case it will be difficult to interpret the results of the build and also the statistics of the builds (for example average build time) will be uninformative. The recommended approach is to create separate build configurations. To simplify the setup you can use build configuration templates.

0

Please sign in to leave a comment.