Skip to content
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

Detect whether vcpkg is running in a CI environment #713

Merged
merged 7 commits into from
Oct 3, 2022

Conversation

vicroms
Copy link
Member

@vicroms vicroms commented Sep 23, 2022

Use well known environment variables to detect whether we are running in a CI environment.

Copy link
Contributor

@ras0219-msft ras0219-msft left a comment

Choose a reason for hiding this comment

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

Two additional notes:

  • Can we test this?
  • Docs

@dg0yt
Copy link
Contributor

dg0yt commented Sep 27, 2022

When vcpkg detects CI environments, can we customize the output to mark error messages, e.g. for AZP?

@vicroms
Copy link
Member Author

vicroms commented Sep 27, 2022

When vcpkg detects CI environments, can we customize the output to mark error messages, e.g. for AZP?

That is a great suggestion! By all means do!

@vicroms vicroms changed the title [telemetry] Detect and track CI environments Detect whether vcpkg is running in a CI environment Sep 27, 2022
@vicroms vicroms marked this pull request as draft September 27, 2022 18:44
@vicroms vicroms force-pushed the telemetry-ci-providers branch 3 times, most recently from bdf5dfc to e1675b7 Compare September 27, 2022 21:26
@vicroms vicroms marked this pull request as ready for review September 27, 2022 21:41
@vicroms vicroms force-pushed the telemetry-ci-providers branch from e1675b7 to 852cf72 Compare September 27, 2022 21:44
Copy link
Member

@BillyONeal BillyONeal left a comment

Choose a reason for hiding this comment

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

I really don't think this test is meaningful because the product bug that's going to happen is a misunderstanding of how those variables are set, and this isn't going to find that.

However, I don't believe it is actively harmful as long as these tests don't take too long to run.

@vicroms vicroms merged commit a447460 into microsoft:main Oct 3, 2022
@vicroms vicroms deleted the telemetry-ci-providers branch October 3, 2022 21:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants