-
Notifications
You must be signed in to change notification settings - Fork 1.4k
Keep track of which global properties/env variables were actually used #3432
Copy link
Copy link
Closed
Labels
Area: DebuggabilityIssues impacting the diagnosability of builds, including logging and clearer error messages.Issues impacting the diagnosability of builds, including logging and clearer error messages.Area: LoggingFeature: Warning WavesWarnings to enable in opt-in waves. Formerly "strict mode".Warnings to enable in opt-in waves. Formerly "strict mode".triaged
Description
Proposal: Every time we use an environment variable or a global property, we should mark it as used, so that we can log which variables were actually consumed during the build.
This would be very useful to determine the "closure" of the build where it depends on the environment. For example, people may inadvertently rely on the "Version" variable, and CI may set that, causing undesired side effects.
Several times now I've seen VSTS CI build breaks because the codebase assumed that Version is of a certain format, and CI was setting it to something else.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
Area: DebuggabilityIssues impacting the diagnosability of builds, including logging and clearer error messages.Issues impacting the diagnosability of builds, including logging and clearer error messages.Area: LoggingFeature: Warning WavesWarnings to enable in opt-in waves. Formerly "strict mode".Warnings to enable in opt-in waves. Formerly "strict mode".triaged
Type
Fields
Give feedbackNo fields configured for issues without a type.