Automatic Release Creation (ARC) validation fails on non-default space

[NickJosevski]

The bug

On a new Space, attempting to user ARC, will fail validation looking for a built in feed that doesn't exist in that Space

What I expected to happen

It should work.

Steps to reproduce

1. On the a Space that's not the default
2. Using a project that has a package step
3. Go to Triggers > ARC > hit setup and select the package step
4. Hit Save 💥

Screen capture

Log exerpt

There was a problem with your request.
The Automatic Release Creation package must be sourced from the Octopus built-in feed.

Affected versions

Octopus Server:
2019.5.4 onwards

Workarounds

None

Links

Issue caused by fix for #5564 in https://github.com/OctopusDeploy/OctopusDeploy/pull/3831

[NickJosevski]

There's another UI related part to this there's a hard coded builtin feed in 1 location.

But it doesn't look to be used: https://github.com/OctopusDeploy/OctopusDeploy/search?q=deploymentActionBuiltInFeedPackages&unscoped_q=deploymentActionBuiltInFeedPackages

Do we have another bug at play or is this just old code that didn't get removed?

https://github.com/OctopusDeploy/OctopusDeploy/search?l=TypeScript&q=feeds-builtin

[NickJosevski]

Fixed in: https://github.com/OctopusDeploy/OctopusDeploy/pull/3926

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. If you think you've found a related issue, please contact our support team so we can triage your issue, and make sure it's handled appropriately.