-
Notifications
You must be signed in to change notification settings - Fork 39
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
[MDS-5515] SchemaSpy updates #2718
Conversation
…ut to test and prod on workflow dispatch
…it from core-api deploy workflows, and try to fix run-if-failed
…a rollout this time
…lls from steps to jobs so context can be added
@@ -77,8 +82,8 @@ jobs: | |||
|
|||
run-if-failed: | |||
runs-on: ubuntu-20.04 | |||
needs: [trigger-gitops] | |||
if: always() && (needs.trigger-gitops.result == 'failure') | |||
needs: [build-backend, build-flyway, trigger-gitops] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
specifically didn't put schemaspy-rollout in here because this notification will say that core-api didn't deploy, and schemaspy has its own notification anyway
|
||
on: | ||
workflow_call: | ||
workflow_dispatch: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Wanted to be able to use workflow_call to have it be triggered from another workflow, and workflow_dispatch, so we can call it manually. Only needed separate files for each to allow manual calls.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice yaml-ing
Objective
MDS-5515
Why are you making this change? Provide a short explanation and/or screenshots