I noticed that the commit hash links in the Build Information part of releases in Octopus Deploy points to the wrong repository. I traced the error back to Teamcity which uses the Octopus Deploy plugin to send build information to Octopus. The step uses a file called “octopus.buildinfo” which seems to contain all the change commits for the build, but only contains one VCS root, even though there are multiple VCS roots configured for the Build Configuration.
I am not sure which part of the Teamcity Octopus Deploy Plugin that generates the octopus.buildinfo file but it does not seem to support multiple VCS roots. I assume that the plugin looks at the “Changes” feature in Teamcity to collect the commits. Since that feature does indeed support multiple VCS roots which are shown in the Teamcity GUI I assume that there’s a bug in the Octopus Deploy integration.
I was hoping to use the Build Information variables in an Octopus Deploy Script step to tag the commits in the git repository I am using. Will there be a fix for this? Preferably adding the repository name to each commit.