Remove disableComponentGovernance parameter from jobs.yml#8471
Conversation
|
Currently running a test for this in this build to verify that the property still gets passed through to the inner jobs that request it: https://dev.azure.com/dnceng/internal/_build/results?buildId=1611693&view=results |
|
@riarenas This might be worth a backport to 3.1/5.0/6.0 too when after verifying in main. |
|
@mmitche Yep I plan to backport wherever it's needed. I'll need another approval as I had previously left in a change only for testing. |
|
Test works: https://dev.azure.com/dnceng/internal/_build/results?buildId=1611693&view=results the linux leg (which I enabled for this test) still has cg, but it's gone from windows as the parameter was forwarded. |
|
Hello @riarenas! Because this pull request has the p.s. you can customize the way I help with merging this pull request, such as holding this pull request until a specific person approves. Simply @mention me (
|
* Remove disableComponentGovernance parameter from jobs.yml * Test disabling cg in the windows leg * remove testing change
* Remove disableComponentGovernance parameter from jobs.yml
* Remove disableComponentGovernance parameter from jobs.yml
* Remove disableComponentGovernance parameter from jobs.yml
#8470
We don't really want to encourage disabling this all throughout a set of jobs, and it's causing issues with disabling it in individual jobs anyways.
To double check: