Related to this I've suggested adding SemVer 2.0.0 support for build information to Channel Version Rules.
This would enable you to match the Channel experimental builds (built with extra debug stuff included) using the build information rather than using version numbers ranges as a proxy for the build metadata.
Found it. I know it was somewhere obscure. It is tucked under the Acceptable User Policy:
"Storage for artifacts, task logs, packages and package cache is limited to 50 GiB."
It is worth reading thw AUP actually. There is not way to backup or migrate from Octopus Deploy Cloud right now, so when the policy says "we reserve the right to suspend or terminate your access to our services without any prior warning or notice." That makes it quite a business risk to adopt the Cloud product.
Hi @Bryan I couldn't find documentation either but I did find the info somewhere unexpected - I forget where now sorry - and it said the ODC package storage limit was 50GB. There was no mention of any option to extend that. It would be nice to know how close to the limit we are.
Why does git support need to be per-proprietary service and not just support any git repo?
As well as the useless top-left menu, having access to a single spaces also causes the 'Configuration' menu item to appear for every user, even though there is nothing they can configure. There is a single section 'Spaces' with a single entry for their one Space.
Upgraded to 2019.x and immediately hit this. It's basically a great big ad in the middle of the application.
Users with access to only one space should not have to put up with the ad or have the prime top-left location wasted on something they have no use for.
We have recently made good progress on getting Tentacle running on Linux via netcore and expect it to be available in the next couple months. https://github.com/OctopusDeploy/Issues/issues/3596
As for Octopus Server on Linux, we have also started working on this effort however the current focus is for internal use for running Hosted Octopus. There are some additional complications that come with running Octopus on Linux particularly in the context of “run on the server” and s a result I wouldn’t expect a version of this to be available until mid-year at the earliest.
Most of our other additional tooling and libraries like Calamari are now available to be run on netcore and run on Linux.