I can’t see what I’ve missed with this.
Source code is in GitHub
Build is done by TeamCity.
We were using Jira & build Info worked fine - tickets mentioned in commits were shown as work items.
We’ve just migrated to Azure DevOps & build info work items don’t work.
I’ve followed the docs:
- PAT setup in Azure Dev Ops with read on build, work items, project & team
- issue tracker added to Teamcity & it recognises commits & work items
- issue tracker added to Octopus & it does not recognise work items
We mention in commits work items using the documented format of AB#99999. I’ve also tried just #99999 just in case, but that didn’t work either.
The url added in the connection in Octopus is https://dev.azure.com//. Clicking test says it works
I’ve removed & disabled the Jira issue trackers from TeamCity & Octopus in case that was causing issues. That made no difference either.
Thanks for reaching out!
Unfortunately Octopus will only consider AzureDevops WorkItems if the
BuildEnvironment value is
Azure Devops also so it’s not currently possible to use other build servers like TeamCity/Jenkins with Azure WorkItems.
This is only really shown in the graphic on the Azure Devops WorkItems doc page, which isn’t very clear so I’ll get a note added about it also:
Feel free to reach out with any questions at all!
That is disappointing. Any plans to change this in the future? I don’t suppose there’s any way to work around this either.
Just jumping in for Finnian as he is currently off shift as part of our Australian based team, I understand having the ability to use Azure Dev Ops Workitems in Octopus from other build servers is something that would be beneficial to you.
I can ask our engineers about this but I doubt we have any plans to implement it at the moment, I can also ask them if there would be any workarounds but we obviously specialise in Octopus, whilst we know a lot about the other build servers we integrate with we do not use them daily so I am not sure if we would have played around with them enough to know any workarounds. I can always ask though.
We do have a features requests page on our Octopus Roadmap (click on the ‘Submit an Idea’ button on the right hand side of the roadmap page).
If you could pop this request in there for us our engineers will see it and possibly consider making it a feature within Octopus!
I will get back to you with what our engineers say but submitting it on our roadmap page would be the first step in order for us to see if we could have it as a feature.