Disabling first time experience in CI
See original GitHub issueWhat are the recommended steps to disable the first time experience and telemetry in CI? Specifically for GitHub Actions. I’ve tried using the environment variables suggested in other issues but this has no impact.
- name: Restore
run: dotnet restore
env:
DOTNET_CLI_TELEMETRY_OPTOUT: 1
DOTNET_SKIP_FIRST_TIME_EXPERIENCE: 1
This still produces the first time output when running restore (on all OS):
Issue Analytics
- State:
- Created 3 years ago
- Comments:16 (13 by maintainers)
Top Results From Across the Web
Disabling GitLab CI/CD
To disable GitLab CI/CD in your project: On the left sidebar, at the top, select Search ... In the Repository section, turn off...
Read more >Disable Code Like Magic With Feature Flags
Disable code in production without touching it. Sound like magic? It's not: gain that power by adopting feature flags.
Read more >How to quickly disable / enable stages in Gitlab CI
5 Answers. You could disable all the jobs from your stage using this trick of starting the job name with a dot ('...
Read more >Monitor Your CI Pipelines and Tests With Datadog CI ...
Learn how Datadog CI Visibility lets you monitor the health and performance of your CI builds and test suite.
Read more >Disable a metric for a CI
Navigate to All > Event Management > Anomaly Detection > Metric to CI. Locate the record for the metric/CI that you want to...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
DOTNET_NOLOGO
does what it’s supposed to withdotnet msbuild
:I think that Jason is expecting it to do the same thing as
/nologo
, which isn’t how it’s documented in either of the two places I could find. (Here and here)It’s probably unnecessarily confusing to have two different concepts use nologo, but I imagine it’s way too late to switch to
DOTNET_NOWELCOME
.@PathogenDavid You are correct. We didn’t have automatic code flow from 3.1 into our .net 5 branches but we have caught up with that PR and are monitoring for additional changes we’ll need in the future so we should be good for a future PR.