Build command line inconsistency about arcade HOT 13 CLOSED

CC @tmat

from arcade.

There appears to be a number of things that are not used or inconsistent in the build.ps1 script. What is our plan and strategy for maintaining that script?

from arcade.

@jaredpar Is it possible to configure PowerShell to allow boolean switches to be passed multiple times?

build.cmd is simply a shortcut for build\Build.ps1 -restore -build
restore.cmd is a shortcut for build\Build.ps1 -restore

I don't really want to make these scripts super-complicated to adjust their help output on what parameters are already specified in the cmd file.

Perhaps we will be able to do something better once we have dotnet local tools feature.

from arcade.

@weshaggard The script is the same across repos using RepoToolset (to be precise, we have 2 variations of the script: one for repos building using VS msbuild and another one for those building using dotnet cli).
Some repos might not need some parameters (like test, integration test, etc.) and that's ok.

Re maintaining - I'm looking into using Meastro to make it easy to update this scriptin all repos easily.

from arcade.

Re maintaining - I'm looking into using Meastro to make it easy to update this scriptin all repos easily.

We have an issue dotnet/buildtools#1709 tracking a similar feature. We should work together to come up with a way to keep these scripts updated.

from arcade.

Is it possible to configure PowerShell to allow boolean switches to be passed multiple times?

Don't think so unfortunately.

I don't really want to make these scripts super-complicated to adjust their help output on what parameters are already specified in the cmd file.

Understood.

Mostly I wanted a way to "restore only". I could invoke build.ps1 directly with that. De-values Build.cmd a bit though.

from arcade.

Mostly I wanted a way to "restore only".

There is restore.cmd in the root.

from arcade.

Understood. I typically only use the build file though.

How do we see the flags build.cmd is passing by default? Maybe that's the solution. Knowing what flags are already set so i know when to go to build.ps1

from arcade.

How do we see the flags build.cmd is passing by default?

Not sure what you mean?

type build.cmd ?

from arcade.

type build.cmd ?

That just tells me the help of the ps1 file. What I'm curious about is what arguments does Build.cmd pass by default. On a Mac at the moment so I'm going off what I'm reading in the Build.cmd file vs. actually executing.

Note: I've run into this exact problem in Roslyn and what we pass by default vs. what is in build.ps1. I don't have a good answer either. Other than possibly change build.ps1 to a different name so that it doesn't have the appearance of being a simple pass through from build.cmd.

from arcade.

Re maintaining - I'm looking into using Meastro to make it easy to update this scriptin all repos easily.

We have an issue dotnet/buildtools#1709 tracking a similar feature. We should work together to come up with a way to keep these scripts updated.

My naïve, yet prototyped, proposal for a similar feature was https://github.com/chcosta/roslyn-tools/blob/bootstrap/docs/Toolset-Bootstrap.md#obtaining-the-toolset

from arcade.

Add to a prodcon epic

from arcade.

Closing because the parent Epic was closed. If you believe this issue should still be worked on, please re-open.

from arcade.