import pipeline-logging-functions during sbom generation prep #10082
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Contributor
Author
mmitche
previously approved these changes
Jul 19, 2022
epananth
approved these changes
Jul 19, 2022
Contributor
Author
|
New test build without my silly typo: https://dev.azure.com/dnceng/internal/_build/results?buildId=1891544&view=results |
riarenas
added a commit
to riarenas/arcade
that referenced
this pull request
Jul 20, 2022
…#10082) * import pipeline-logging-functions during sbom generation prep
riarenas
added a commit
that referenced
this pull request
Jul 21, 2022
#10094) * import pipeline-logging-functions during sbom generation prep
am11
pushed a commit
to am11/arcade
that referenced
this pull request
Jul 26, 2022
…#10082) * import pipeline-logging-functions during sbom generation prep
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Found this during testing of dotnet/arcade-services#1951.
We use the telemetry logging functions in the scripts, but we never imported them and I think this has been working out of sheer luck that other steps in the build had imported these functions previously.
To double check: