From 489d0ff1a6ba390757c02d09792fd5bd83fe2976 Mon Sep 17 00:00:00 2001 From: Niels de Vos Date: Thu, 29 Jun 2023 12:26:41 +0200 Subject: [PATCH] doc: remove `/retest all` command for Jenkins jobs `/retest all` causes a spike in resource consumption in Jenkins and the OpenShift cluster kills the Pod. That means tests are not fully running yet, and results never arrive back in the PR. Instead of `/retest all`, the `ok-to-test` label can be used to trigger required tests with a slight delay between each command. Signed-off-by: Niels de Vos --- .github/pull_request_template.md | 2 -- docs/development-guide.md | 6 ------ 2 files changed, 8 deletions(-) diff --git a/.github/pull_request_template.md b/.github/pull_request_template.md index 0a76f23a5..70e2f6d1e 100644 --- a/.github/pull_request_template.md +++ b/.github/pull_request_template.md @@ -44,7 +44,5 @@ the following bot commands in an otherwise empty comment in this PR: - `/retest ci/centos/`: retest the `` after unrelated failure (please report the failure too!) -- `/retest all`: run this in case the CentOS CI failed to start/report any test - progress or results diff --git a/docs/development-guide.md b/docs/development-guide.md index 4e84c16cf..da57a3e15 100644 --- a/docs/development-guide.md +++ b/docs/development-guide.md @@ -300,12 +300,6 @@ opening fresh PRs, rebase of PRs and force pushing changes to existing PRs. Right now, we also have below commands to manually retrigger the CI jobs -1. To retrigger all the CI jobs, comment the PR with command: `/retest all` - - **Note**: - - This will rerun all the jobs including the jobs which are already passed - 1. To retrigger a specific CI job, comment the PR with command: `/retest ` example: