Closed m-nash closed 1 week ago
For now @ArthurMa1978 please run /azp run net - [ServiceDirectory]- mgmt - ci
for each rp one at a time to not clog the build system but still get the coverage
EDIT: actually this doesn't work because it gives the following error. @weshaggard please advise
For triggering the pipeline manually run /azp run net - [ServiceDirectory] - mgmt
instead.
@sima-zhu once you get the work done to run the core pipeline code gen step in parallel done, can you also please do the same for the resourcemanager pipeline?
@sima-zhu can you have an ETA of fixing this issue?
After further conversation we did not end up enabling this for the core pipeline because it turns out it is not needed so we removed the *
from there. I was thinking we would do the same thing (i.e. not enable this) for resourcemanager however I just realized we disabled all the individual mgmt pipelines from triggering so we probably do still need this support for resourcemanager.
@sima-zhu can you use your work you did for core and try enabling it for resourcemanager pipeline as we do need to check all the mgmt libraries in this case.
Analyze Step, check the box if it supports the project list
service.proj
eng/common
. Scan the changes under eng/common
For most of the tasks, support service directories is much easier than support project list.Further categorizations:
eng/common
The steps in Build
The steps in Compliance
:
@sima-zhu and @weshaggard The original intention of this issue is now complete. Are we using this issue to track follow up work as well or is it safe to close this?
I'd like to keep this open for now because what we have is still in testing from my perspective.
@benbp this is a case study when you start thinking about the pipeline changes.
Hi @m-nash, we deeply appreciate your input into this project. Regrettably, this issue has remained unresolved for over 2 years and inactive for 30 days, leading us to the decision to close it. We've implemented this policy to maintain the relevance of our issue queue and facilitate easier navigation for new contributors. If you still believe this topic requires attention, please feel free to create a new issue, referencing this one. Thank you for your understanding and ongoing support.
Library name and version
Azure.ResourceManager
Describe the bug
We recently updated the ci for mgmt to only run
net - resourcemanager - mgmt - ci
for all mgmt plane libraries instead of individual ci's due to performance reasons. Commit is here. In the latest run here I noticed that the analyze step is only running for Azure.ResourceManager and NOT all of the other mgmt projects.Our analyze step is able to deal with
*
as a ServiceDirectory and auto-expand we probably need to adjust that to treatresourcemanager
as a wild card as well and run each mgmt library.To find all mgmt projects we can use this code here. This excludes Azure.ResourceManager which we probably want to include when running analyze so just remove the extra
.
at the end of the filter.Expected behavior
All mgmt plane libraries have their analyze step run
Actual behavior
only resourcemanager library has its analyze step run
Reproduction Steps
run the net - resourcemanager - mgmt - ci
Environment
No response