Skip to content
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.

Sign up for GitHub

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

Jump to bottom

docs: Document how to run tests on backport PRs #11211

Merged
merged 1 commit into from
Apr 29, 2020
Merged

docs: Document how to run tests on backport PRs #11211

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
8 changes: 8 additions & 0 deletions Documentation/contributing/release/backports.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Expand Down
4 changes: 4 additions & 0 deletions Documentation/contributing/testing/ci.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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:

Expand Down