We have recently upgraded Octopus Deploy 2021.1 (from 2017.8) we are using an internal Nexus Repository for our nupkg feed. We have a unique packaging and naming format… its not pure semver
Within the release pipeline “Deploy a Package” step . it only appears to like packages that have more straightforward naming conventions.
for example
2021.4.0 works.
but more complex build ids like 2021.4.0.0-11.50.210609.aabbccc will not work… (we need to use this format) and it worked ok in 2018.7
otherwise we get a red message “The package was not found in the feed”
Assuming the version 2021.4.0.0-11.50.210609.aabbccc is an exact example, the problem with this one is that before the dash you can only have 2 dots. If you make it 2021.4.0-11.50.210609.aabbccc instead, it will work.
Unfortunately, in our newer versions, valid semver is required. You can use a semver checker online to ensure that the rules are being followed.
Please let me know if it looks like your versioning works in a semver checker and yours is also another case of the above issue, or if you have any other questions or concerns.
We have recently upgraded to Azure DevOps Server 2020 (from TFS 2017.1) and Octopus Deploy 2021.1 (from 2018.7).
We are not able to pull in projects from Octopus Deploy to Azure DevOp within the Releases.
I have created a connection to Octopus using an Octopus Service Account / with API Key – using FQDN over https and server name via http.
Added Azure DevOps Server url to CORS list on Octopus. (also changed to * to test also)
Upgraded the Azure DevOps Octopus Deploy Integration extension from 2.0.44 (used in TFS) to 4.2.472
I can see from the above ticket version 2 does not work. I have tried V3 and V4 and get the same error in the Azure DevOps browser console Data source with name OctopusAllProjects could not be found for the given service
We don’t have any “Spaces” used just the “default” but nothing appears in any of the drop downs.