ci: send notifications to teams channel #895
Conversation
katexochen
changed the title
| run: | | ||
| curl \ | ||
| -H "Content-Type: application/json" \ | ||
| -d '{"workflow_name": "${{github.workflow}}", "job_id": "${{github.job}}", "run_id": "${{github.run_id}}", "ref": "${{github.ref_name}}", "message": "${{inputs.message}}"}' \ |
There was a problem hiding this comment.
Can we quote the message string, or at least document what it may and may not contain?
There was a problem hiding this comment.
Seems like quoted strings just disappear from the message, should I just document this in the description of the workflow run?
There was a problem hiding this comment.
Documented this behavior in the description of the message parameter.
|
We should use a card like with Constellation and provide a direct link/button to the logs. |
miampf
force-pushed
the
miampf/e2e/send-notifs-to-teams
branch
2 times, most recently
from
7aa21c1 to
c6f2707
Compare
better message
mod message
miampf
force-pushed
the
miampf/e2e/send-notifs-to-teams
branch
3 times, most recently
from
c0610fc to
5762ce9
Compare
Cards are now posted in the corresponding channel. |
Button to run seems to be broken? |
I don't think the buttons are broken, its just that the messages I sent contained quotes which seemingly broke the parsing of the workflow and caused the URL to be replaced with the last word of the quoted text. If you look at the card with run_id 11177841920 (which uses the same adaptive card layout) you'll see that the button works there :) |
| shell: bash | ||
| run: | | ||
| run_url="${{github.server_url}}/${{github.repository}}/actions/runs/${{github.run_id}}" | ||
| payload="$(printf '{"workflow_name": "%s", "job_id": "%s", "run_id": "%s", "ref": "%s", "message": "%s", "run_url": "%s"}' \ |
There was a problem hiding this comment.
as this gets more complex, we might want to have a template file, similar to the one in constellation.
Add the
post_to_teamsgithub action that allows a workflow to post into theContrast-CI-Notificationschannel. Furthermore, integrate this action into weekly running actions.