docs: Document how to run tests on backport PRs

These long-lost incantations were thought forfeited to history, but we were able to unearth but a few survivors who recall how to use them... Signed-off-by: Joe Stringer <joe@cilium.io>
cilium · Apr 29, 2020 · 4594e6a · 4594e6a
1 parent c8db262
commit 4594e6a
Show file tree

Hide file tree

Showing 2 changed files with 12 additions and 0 deletions.
diff --git a/Documentation/contributing/release/backports.rst b/Documentation/contributing/release/backports.rst
@@ -189,6 +189,14 @@ Via GitHub web interface
    the ``start-backport`` script above (``GITHUB_TOKEN`` needs to be set for
    this to work).
 
+Running the CI against the pull request
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+To validate a cross-section of various tests against the PRs, backport PRs
+should be validated in the CI by running all CI targets. This can be triggered
+by adding a comment to the PR with exactly the text ``never-tell-me-the-odds``.
+The comment must not contain any other characters.
+
 After the backports are merged
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 

diff --git a/Documentation/contributing/testing/ci.rst b/Documentation/contributing/testing/ci.rst
@@ -204,6 +204,10 @@ illustrating which subset of tests the job runs.
 |                                                                                                                | test-gke          |                    |
 +----------------------------------------------------------------------------------------------------------------+-------------------+--------------------+
 
+For Backport PRs, the phrase ``never-tell-me-the-odds`` should be used to
+trigger all of the above jobs which are marked as required to validate changes
+to existing releases.
+
 There are some feature flags based on Pull Requests labels, the list of labels
 are the following: