fs-integration: Avoid running full test suite always for GlusterFS #42
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
anoopcs9
force-pushed
the
gfs-build-gh-label
branch
from
6cd8e40 to
ae49f85
Compare
anoopcs9
force-pushed
the
gfs-build-gh-label
branch
from
ae49f85 to
8867bce
Compare
spuiuk
approved these changes
Nov 14, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hereafter require a GitHub label(
centos-ci/glusterfs) on pull requests against sit-test-cases repository to trigger full test suite run for GlusterFS.Please note that in addition to setting the required label corresponding keywords are to be made as GitHub comment to trigger the job. In this case a comment in the form
/test centos-ci/glusterfsor/retest centos-ci/glusterfsis expected after centos-ci/glusterfs label is set on the pull request. This extra step can't be avoided due to an open issue jenkinsci/ghprb-plugin#496