Azure DevOps extension automatic space search

resolved
server
reliability
external
(Jp Roussel) #1

Hi,

I have created a service connection for Octopus on our Azure DevOps project - using the projects API key & ignoreSslErrors is checked.
In the release pipeline we use the Push Package(s) to Octopus job.
Should the Space automatically resolve to what is on our Octopus Server (see image below)?

(Paul Calvert) #3

Hi @jp.roussel,

Thanks for getting in touch!

You are correct, it should query the Octopus Server and provide a list of available Spaces. You can try using the refresh button to the right to see if that helps the list generate, otherwise there may be an issue with the connectivity between Azure DevOps and your Octopus Server.

e.g.

Just to check too, are you using a version of Octopus Server that includes the Spaces feature (v2019.1+)?

Best regards,
Paul

(Jp Roussel) #4

I assumed as much. Will have to investigate and get back to you.

Yes we are, v2019.12. I can view the space name on Octopus and used it in Team City - we have to sadly migrate away from Team City now.

(Paul Calvert) #5

You could try manually adding the Space name and running the build, it may provide a clearer error to help track down the issue.

(Jp Roussel) #6

I was using the incorrect Agent Pool. We have an on-prem agent setup

1 Like