Using a hardcoded commit id in git VCS root
At Oticon we have a number of different projects working together throught git - this means a lot of git repos and a lot of tags to keep track of the version of git VCS's to use.
In some cases one project will use a specific git commit id/hash as the version to use of another project.
I have been unable to figure whether the refs/heads/blah and refs/tags/stuff default branch specification allows specifying a specific commit id/hash - if that is possible it would solve my problem right away.
We auto-generate all over VCS root (and projects for that matter) - so it does not matter that the syntax is cumbersome, as long as i it works.
Please sign in to leave a comment.
Hi,
I'm afraid that it's not possible to specify a single revision to be the one to be used in a VCS Root, although this should be possible to work around, depending on what your exact scenario would be.
The easiest way to get that would be to set up a specific branch with that revision that is used as reference. You could use tags as well instead of branches. Also keep in mind that you can use parameter references in the VCS Roots, so you could share the same VCS Root among multiple projects and configurations, but on the specific projects or build configurations where you need them to stick to a specific revision, you could override the parameter from the build configurations.
For other possible solutions we would need to understand your scenario in more detail before we can provide other suggestions.