Skip to content

Avoid changing global state in CI runs #21602

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
May 8, 2020
Merged

Conversation

dougbu
Copy link
Contributor

@dougbu dougbu commented May 8, 2020

  • set $env:DOTNET_CLI_HOME because we need to install global tools in this repo
  • without this, we see dotnet-serve installation failures on unclean machines

- set `$env:DOTNET_CLI_HOME` because we need to install global tools in this repo
- without this, we see `dotnet-serve` installation failures on unclean machines
@dougbu dougbu requested review from sebastienros, captainsafia and a team May 8, 2020 00:01
@ghost ghost added the area-infrastructure Includes: MSBuild projects/targets, build scripts, CI, Installers and shared framework label May 8, 2020
@dougbu
Copy link
Contributor Author

dougbu commented May 8, 2020

@dotnet/efcore I'm not sure whether a similar change would be useful in dotnet/ef6 or dotnet/efcore. Does anything in your pipeline install a global tool❔

@javiercn, @NTaylorMullen, @pranavkm what about aspnetcore-tooling❔

(The repos that aren't dotnet/aspnetcore don't use .config/dotnet-tools.json. But, that isn't clear enough to be sure about global tool use.)

@pranavkm
Copy link
Contributor

pranavkm commented May 8, 2020

@NTaylorMullen \ @ajaybhargavb would know best, but afaik tooling doesn't require a global tool.

Copy link
Member

@captainsafia captainsafia left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for taking the time to do this.

@pranavkm pranavkm merged commit 307350e into master May 8, 2020
@pranavkm pranavkm deleted the dougbu/add.DOTNET_CLI_HOME branch May 8, 2020 02:20
@dougbu
Copy link
Contributor Author

dougbu commented May 8, 2020

Turns out this change was incomplete because I didn't add the .dotnet/tools directory to the path. It'll work until the 'blazor-wasm' branch is merged into 'master'. I'll send a follow up tomorrow.

dougbu added a commit that referenced this pull request May 11, 2020
- set `$env:DOTNET_CLI_HOME` because we need to install global tools in this repo
- without this, we see `dotnet-serve` installation failures on unclean machines
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-infrastructure Includes: MSBuild projects/targets, build scripts, CI, Installers and shared framework
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants