I am making my first experimentation with spaces. My newly created space cannot see any of the existing packages in the (I presume default space) Library, but I cannot work out how to get my Team City to push one to the Space’s specific library.
Thanks for getting in touch! With the addition of spaces, we added the --space=VALUE argument in Octo.exe (which is what the TeamCity plugin uses under the hood). You can add this as an additional command line argument in your TeamCity push step to push to a specific space. This may require an update to your TeamCity plugin if you’re using an older version.
I hope this helps! Let me know how you go or if you have any further questions or concerns moving forward.
You’re very welcome, I’m very happy to hear it’s been helpful!
Publishing a package to a non-default space should just work by specifying the space ID in the URL you have defined in the Publish packages to HTTP field (e.g. http://localhost:7050/spaces-ID/nuget/packages, and not specifying a space ID here just publishes to the default space). However I haven’t had a chance to give this a confirmation test and we haven’t added this yet to our docs. I’d be very keen to hear if this works as we expect.
I first assumed it wanted the NAME of the space, because that seems to be the pattern in most places. Didn’t work.
I then guessed the ID must be some internal value. Is it formally displayed anywhere in the UI? I guessed it from looking at the url’s that the admin tool uses. So for me Spaces-2 was perfect.
That’s great to hear the space ID added to the URL worked correctly! Thank you for letting me know the outcome, and I’ll make sure to update our docs soon to include this.
The space ID displays in the URL when in the UI (it will display as OctoURL/app#/Spaces-ID/...). Alternatively, you can grab them from the API at OctoURL/api/spaces/all.
Don’t hesitate to reach out if you have any questions or concerns in the future!