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.

Sign up for GitHub

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

Disable component governance in Linux_musl_x64_build #39898

Merged
merged 1 commit into from
Feb 1, 2022
Merged

Disable component governance in Linux_musl_x64_build #39898

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions .azure/pipelines/ci.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -520,6 +520,7 @@ stages:
$(_PublishArgs)
$(_InternalRuntimeDownloadArgs)
installNodeJs: false
disableComponentGovernance: true
skipComponentGovernanceDetection: true
Copy link
Member

Choose a reason for hiding this comment

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

do we still need skipComponentGovernanceDetection and the GC_RAN build step in default-build.yml❔

Copy link
Member Author

Choose a reason for hiding this comment

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

I adopted a "if it ain't broke don't fix it mentality here". It appears to me that if disableComponentGovernance and skipComponentGovernanceDetection are set to the same value, then the same behavior will persist.

artifacts:
- name: Linux_musl_x64_Logs
Expand Down