Closed bebound closed 1 week ago
However, it can detect all setup.py
in azure-cli-extension repo: https://dev.azure.com/azclitools/public/_build/results?buildId=164277&view=logs&j=24167955-3a21-598f-f417-ac72576ccfb5&t=7b6ea8ea-a305-55bf-b00f-1b6260132803
In azure-cli, it shows Running self-contained version of Component Detection with version v0.1.0.
In azure-cli-extension, it shows Running self-contained version of Component Detection with version v0.1.6
.
But this is an auto-injected task, I don't know why the version is different.
I checked the pipeline, it uses Running self-contained version of Component Detection with version v0.1.8.
now and the issue is fixed.
It seems that it started on June 4 and was finally fixed on June 7.
We have several
setup.py
in our repo: https://github.com/Azure/azure-cli The auto-injected Component Detection in ADO can only find the firstsetup.py
:/s/tools/setup.py
However,
src/azure-cli/setup.py
,src/azure-cli-core/setup.py
,src/azure-cli-telemetry/setup.py
andsrc/azure-cli-testsdk/setup.py
are missing.Here is the log: https://dev.azure.com/azclitools/public/_build/results?buildId=162225&view=logs&jobId=15c91363-8619-578d-3fff-3c1a2fde03cd&j=e725b3e9-648f-510f-a0a1-f18bdc151d12&t=ea579b3c-b4c1-59de-db37-e3a24fdd50a7
gc log.txt