-
Notifications
You must be signed in to change notification settings - Fork 5k
Fix update-Mgmt-CI.ps1 to unblock release planner #50137
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.
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
Comments
Hi @ArthurMa1978, I'm an AI Support assistant here to help with your issue. While the Azure SDK team reviews your request, I wanted to provide some possible tips and documentation that might help you in the meantime.
The Azure SDK team will respond to your issue shortly. I hope these suggestions are helpful in the meantime. If this comment helped you, please give it a 👍. If the suggestion was not helpful or incorrect, please give it a 👎. Your feedback helps us improve! |
The recent change to the storage/ci.yml is the root cause. The script update-Mgmt-CI.ps1 only works with a specific input format of ci.yml. This simple modification to the storage/ci.yml can resolve the issue. The expected format should be like the following (as in the appconfiguration/ci.ym, single include for service directory path followed by one or more exclude paths) with the current storage/ci.yml, the AutoPR generated from other resource, as shown in here, will incorrectly add additional lines into storage/ci.yml |
@haiyuazhang, @ArthurMa1978: This is an issue in your script that needs to be fixed. You should not assume any specific form of ci.yml, as packages will extend to meet their own unique needs. Also, that automated PR is straight-up wrong. It should NEVER modify configuration outside of the /sdk area that it is running. |
Ray confirmed update-Mgmt-CI.ps1 can be and will be deprecated. This is the issue he created to track the deprecation work. With that, we can close this one. |
Currently, the update-Mgmt-CI.ps1 script updates the CI file incorrectly for Storage and needs to be fixed.
The text was updated successfully, but these errors were encountered: