Movatterモバイル変換

[0]ホーム
URL:

Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

 Sign up
Appearance settings

Commit98c72c3

Browse files
ci: make blink ci failure prompt a gha variable (#19633)
Got sick of seeing blink create duplicates, so I'm updating the prompt. To make it configurable without committing I'm making it a variable, here's what I've got:> Investigate this CI failure. Check logs, and figure out what went wrong. Search for existing issues in coder/internal. If an issue for the CI failure does not exist already, create one ONLY in coder/internal. Do NOT create duplicate issues. Use title format \"flake: TestName\" for flaky tests, and assign them to the person from git blame.If multiple tests fail with the reason `unknown`, the test process exited unexpectedly, perhaps due to a panic.Once blink supports per-slack-channel contexts, i'll probably just set the variable to the empty string and use that instead.
1 parenta8f92cb commit98c72c3

File tree

2 files changed

+6
-2
lines changed

2 files changed

+6
-2
lines changed

‎.github/workflows/ci.yaml‎

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1614,6 +1614,7 @@ jobs:
16141614
steps:
16151615
-name:Send Slack notification
16161616
run:|
1617+
ESCAPED_PROMPT=$(printf "%s" "<@U08TJ4YNCA3> $BLINK_CI_FAILURE_PROMPT" | jq -Rsa .)
16171618
curl -X POST -H 'Content-type: application/json' \
16181619
--data '{
16191620
"blocks": [
@@ -1653,11 +1654,12 @@ jobs:
16531654
"type": "section",
16541655
"text": {
16551656
"type": "mrkdwn",
1656-
"text":"<@U08TJ4YNCA3> investigate this CI failure. Check logs, search for existing issues, use git blame to find who last modified failing tests, create issue in coder/internal (not public repo), use title format \"flake: TestName\" for flaky tests, and assign to the person from git blame."
1657+
"text":'"$ESCAPED_PROMPT"'
16571658
}
16581659
}
16591660
]
16601661
}' "${SLACK_WEBHOOK}"
16611662
env:
16621663
SLACK_WEBHOOK:${{ secrets.CI_FAILURE_SLACK_WEBHOOK }}
16631664
RUN_URL:"${{ github.server_url }}/${{ github.repository }}/actions/runs/${{ github.run_id }}"
1665+
BLINK_CI_FAILURE_PROMPT:${{ vars.BLINK_CI_FAILURE_PROMPT }}

‎.github/workflows/nightly-gauntlet.yaml‎

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -170,6 +170,7 @@ jobs:
170170
steps:
171171
-name:Send Slack notification
172172
run:|
173+
ESCAPED_PROMPT=$(printf "%s" "<@U08TJ4YNCA3> $BLINK_CI_FAILURE_PROMPT" | jq -Rsa .)
173174
curl -X POST -H 'Content-type: application/json' \
174175
--data '{
175176
"blocks": [
@@ -209,11 +210,12 @@ jobs:
209210
"type": "section",
210211
"text": {
211212
"type": "mrkdwn",
212-
"text":"<@U08TJ4YNCA3> investigate this CI failure. Check logs, search for existing issues, use git blame to find who last modified failing tests, create issue in coder/internal (not public repo), use title format \"flake: TestName\" for flaky tests, and assign to the person from git blame."
213+
"text":'"$ESCAPED_PROMPT"'
213214
}
214215
}
215216
]
216217
}' "${SLACK_WEBHOOK}"
217218
env:
218219
SLACK_WEBHOOK:${{ secrets.CI_FAILURE_SLACK_WEBHOOK }}
219220
RUN_URL:"${{ github.server_url }}/${{ github.repository }}/actions/runs/${{ github.run_id }}"
221+
BLINK_CI_FAILURE_PROMPT:${{ vars.BLINK_CI_FAILURE_PROMPT }}

0 commit comments

Comments
 (0)
[8]ページ先頭
©2009-2025 Movatter.jp