Include TeamCity changes links with each Release
It would be great to integrate links to the TeamCity changes included in each Release when using TeamCity's nuget feed as a source for deployment packages
The suggestion by Rob (to include it in the release notes when using Octo.exe) is a good one. Alternatively you could modify the way your NuGet packages are built to include the changes link in the element of the .nuspec. Both of these approaches would be preferred since they don’t require Octopus to make any assumptions about TeamCity usage.
Amrendra prasad commented
HI , I am facing an issue related to CI/CD deployment. Actually i am using Synonym in my DB projects for cross db reference. So when we uses the Synonym in DB project then DB project running fine and publish is also working fine using db projects. But when we are using same code through CI/CD deployment then it shows some error. So any one suggest to me how can use Synonyms in CI/CD release.
This (well documented!) solution shows actual log messages in Octopus:
Chase Florell commented
I've wired up a script that does this. Works pretty well.
We accomplished this by having the final step of TeamCity actually building the release using the octo.exe API. When then add as the releasenotes parameter this: https://teamcity/viewLog.html?buildTypeId=bt101&buildId=%teamcity.build.id%';
This will create a hyperlink in the Octopus release notes.