mirrors/ceph-csi
1
0
Fork 0
mirror of https://github.com/ceph/ceph-csi.git synced 2024-11-22 14:20:19 +00:00
Code Issues Packages Projects Releases Wiki Activity

doc: remove /retest all command for Jenkins jobs

Browse Source 
`/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 <ndevos@ibm.com>
This commit is contained in:
Niels de Vos 2023-06-29 12:26:41 +02:00 committed by mergify[bot]
parent ebfd915ad6
commit 489d0ff1a6
2 changed files with 0 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
.github/pull_request_template.md vendored
View File

@ -44,7 +44,5 @@ the following bot commands in an otherwise empty comment in this PR:
- `/retest ci/centos/<job-name>`: retest the `<job-name>` after unrelated - `/retest ci/centos/<job-name>`: retest the `<job-name>` after unrelated
failure (please report the failure too!) failure (please report the failure too!)
- `/retest all`: run this in case the CentOS CI failed to start/report any test
progress or results
</details> </details>

6
docs/development-guide.md
View File

@ -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 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 <job-name>` 1. To retrigger a specific CI job, comment the PR with command: `/retest <job-name>`
example: example: