-
Notifications
You must be signed in to change notification settings - Fork 183
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
Swagger APIView PR pipeline automation reports success and failure #5941
Labels
Comments
ghost
added
the
needs-triage
Workflow: This is a new issue that needs to be triaged to the appropriate team.
label
Apr 10, 2023
I have retriggered the pipeline ... hoping that this will resolve the problem. |
maririos
added
APIView
Central-EngSys
This issue is owned by the Engineering System team.
and removed
needs-triage
Workflow: This is a new issue that needs to be triaged to the appropriate team.
labels
Apr 10, 2023
You are right the Job should be shown as failed since the APIView step failed. I will get this resolved. |
Here is another instance: PR 23616 It looks like the failure was:
I retriggered the pipeline. |
I have a PR out for this https://dev.azure.com/devdiv/DevDiv/_git/openapi-alps/pullrequest/468763 |
github-project-automation
bot
moved this from 🤔 Triage
to 🎊 Closed
in Azure SDK EngSys 🚢🎉
May 8, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In PR 23091 the Swagger APIView PR pipeline automation is reporting success:
AND failure:
The text was updated successfully, but these errors were encountered: