[darc/maestro++] darc doesn't use Arcade CLI about arcade-services HOT 9 CLOSED

.net cli supports "local" global tools.

from arcade-services.

@chcosta This is an interesting scenario. Where does the darc tool get installed in this case? I'm not sure what the expected behavior is, since this is a dotnet global tool. Maybe the dotnet toolset needs to make it on the PATH?

Or maybe dotnet global tools don't work at all if the sdk isn't on the PATH. @livarcocc What is the expected behavior if you:

• Didn't have the dotnet SDK on the path
• Explicitly called some SDK to install a tool
• Called the tool.

from arcade-services.

@livarcocc - curious if you have thoughts here

from arcade-services.

Darc is not really local to a repo, it just happens to be rolled out that way. You could install it "locally". but as soon as you clean your enlistment, darc will be gone. I think "local" is more confusing tbh.

Anyways, I don't think a fix for this is required for p2.

from arcade-services.

The rest of Arcade follows the pattern that if you're running locally, then you install things globally (default) and this helps with things like package restores such; if you're running in ci, then packages are installed locally, this prevents machine wide state issues. It'd be great to follow a similar pattern with darc.

It's confusing to have this thing that is delivered with Arcade but doesn't use or follow any of the Arcade conventions (including CLI version)

Agreed, I don't think this is required for p2.

from arcade-services.

@chcosta It's actually no longer delivered with arcade (aside from install script).

from arcade-services.

I think that's my main concern though. The perception is that, since you get the install script from Arcade (eng/common), that it follows Arcade conventions. Perhaps this shouldn't be delivered via Arcade?

from arcade-services.

Maybe we should just not have it bootstrap the dotnet toolset all all and require a global toolset? The install script can still be delivered via arcade. It's just looking up the correct version to use and doing a dotnet tool install

from arcade-services.

I created this related issue yesterday, dotnet/arcade#3744

On NuGet side we're basically writing a release definition that bootstraps darc, and then does a add-build-to-channel and trigger subscriptions.

from arcade-services.