Skip to content

Only retry deploy tests for canary #81207

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

Merged
merged 2 commits into from
Jul 3, 2025
Merged

Only retry deploy tests for canary #81207

merged 2 commits into from
Jul 3, 2025

Conversation

ijjk
Copy link
Member

@ijjk ijjk commented Jul 3, 2025

This avoids retrying/alerting if triggering the deploy tests with a custom next tarball. The run_name is available as display_title per docs here

x-ref: slack thread

@ijjk ijjk added the created-by: Next.js team PRs by the Next.js team. label Jul 3, 2025
@ijjk ijjk requested review from ztanner, gaojude and RobPruzan July 3, 2025 01:27
@ijjk ijjk merged commit ca8a066 into canary Jul 3, 2025
83 of 140 checks passed
@ijjk ijjk deleted the ijjk/e2e-deploy-alert branch July 3, 2025 02:46
ijjk added a commit that referenced this pull request Jul 3, 2025
@@ -18,6 +18,7 @@ jobs:
# Retry the test-e2e-deploy-release workflow up to 2 times
if: >-
${{
github.event.workflow_run.display_title == 'test-e2e-deploy canary'
Copy link
Member

Choose a reason for hiding this comment

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

What happens with backports?

Copy link
Member

Choose a reason for hiding this comment

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

I don't think we run these automatically on backports, but I'd expect whoever manually triggers them takes a look at the job afterwards.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
created-by: Next.js team PRs by the Next.js team.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants