Skip to content

chore: add slack success post on nightly scenario#21701

Merged
danielntmd merged 1 commit intomerge-train/spartanfrom
danielntmd/post-slack-scenario-success
Mar 17, 2026
Merged

chore: add slack success post on nightly scenario#21701
danielntmd merged 1 commit intomerge-train/spartanfrom
danielntmd/post-slack-scenario-success

Conversation

@danielntmd
Copy link
Contributor

Will report both legs of the scenario tests.

@danielntmd danielntmd requested a review from charlielye as a code owner March 17, 2026 18:29
@danielntmd danielntmd removed the request for review from charlielye March 17, 2026 18:37
ci3/run_test_cmd Outdated
fi

if [ "$slack_notify_pass" -eq 1 ]; then
slack_notify "Test PASSED on *${TARGET_BRANCH:-$REF_NAME}*: \`$test_cmd\` $DASHBOARD_URL/$log_key" "#alerts-next-scenario"
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

hmm why both?
my preference is to have the slack posted inside the ci job handling, not here nor in in GA but in bootstrap.sh with a call like this

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Very simple PR now. It's both still because bootstrap.sh can't keep track of both deployment states.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If we want 1 message, we need a downstream GA job in ci3.yml

@danielntmd danielntmd force-pushed the danielntmd/post-slack-scenario-success branch 3 times, most recently from de9e2e1 to 7bef3ef Compare March 17, 2026 19:11
Copy link
Collaborator

@ludamad ludamad left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@danielntmd danielntmd enabled auto-merge March 17, 2026 19:15
@danielntmd danielntmd force-pushed the danielntmd/post-slack-scenario-success branch from 7bef3ef to 4c2210e Compare March 17, 2026 19:20
@danielntmd
Copy link
Contributor Author

Sorry for push after review, added extra label to distinguish which scenario set passed.

@danielntmd danielntmd merged commit 1827411 into merge-train/spartan Mar 17, 2026
11 checks passed
@danielntmd danielntmd deleted the danielntmd/post-slack-scenario-success branch March 17, 2026 19:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants