Hi,
I’m using Octopus Deploy with TFS. I’m able to create a TFS build for Octopus.
Now, I would like to solve the traceability issue.
When I open a package, I would like to know what changeset (not the comments, I don’t care, just the changeset id) was used to produce this package. But how can we solve this problem?
I’m using the version from assembly version attribute and automatic release creation.
One solution would be to add a custom activity in the TFS which create a ReleaseNotes file with the build number and the changeset id, then we can pass this releasenotes file with the argument OctoPackReleaseNotesFile. But I’m already using a changelog file where we put the changes between versions. So I have to merge these files.
Is there a better solution?
I’ve found these articles :
http://blog.nwcadence.com/inserting-team-build-number-into-the-octopack-run-version-for-a-nuget-package/ : Not what I want, because I want to use assembly version.
https://dejanvasic.wordpress.com/2012/09/27/tfs-build-ci-octopusdeploy-nuget-website-deploys/ : I don’t really like this solution, you always have to change the version during the build, I prefer to use assembly version.
It’s a kind related to this http://help.octopusdeploy.com/discussions/questions/5012-get-tfs-build-number-in-nuget-package-description
Thanks!