The test names must match exactly for the mergify
auto merge to complete successfully. Update two of
the test names to match the latest CI.
Signed-off-by: Travis Nielsen <tnielsen@redhat.com>
(cherry picked from commit 83b017994e)
For nightly jobs, canary tests are all running with the same job IDs,
making the last-run jobs cancel previous runs. Add a workflow-id
parameter to canary jobs that can be used to give each job in a canary
suite a unique job ID to prevent this.
Signed-off-by: Blaine Gardner <blaine.gardner@ibm.com>
Add mergify rules for opening backport PRs to the release-1.13
branch and also for auto-merging backports after the CI
passes.
Signed-off-by: travisn <tnielsen@redhat.com>
updating .mergify backport for 1.12 branch
to include latest version of k8s v1.28.0 and
latest golang version v1.21.0
Signed-off-by: subhamkrai <srai@redhat.com>
For the new release-1.12 branch, mergify rules are added
for automatically opening PRs and merging backports
when approved.
Signed-off-by: travisn <tnielsen@redhat.com>
The multi-cluster-mirroring test is consistently failing.
Any failing tests will prevent mergify from merging the
backport PRs automatically, so we disable this until
that test passes.
Signed-off-by: Travis Nielsen <tnielsen@redhat.com>
Add the mergify settings so backports can be automated
to the release-1.11 branch and automatically merged
after the CI is green.
Signed-off-by: Travis Nielsen <tnielsen@redhat.com>
The success of all the CI actions must exactly match the
list for the mergify config. The config was missing a
paren, so the merges were not happening automatically.
Signed-off-by: Travis Nielsen <tnielsen@redhat.com>
Rook will support the most recent seven K8s releases,
so we update the min version to 1.19 for Rook v1.10.
Signed-off-by: Travis Nielsen <tnielsen@redhat.com>
Configure the mergify bot to open backport PRs for the
1.10 release branch if PRs are labeled as such.
Signed-off-by: Travis Nielsen <tnielsen@redhat.com>
Support is removed for k8s for various limitations such as
priority classes not working and csi driver feature
incompleteness and missing snapshots. Documentation is updated
with the new min version of k8s 1.17 and also the tests are
updated to run on the min version of 1.17.
Signed-off-by: Travis Nielsen <tnielsen@redhat.com>
The ibm test is not expected to run in PRs, so we can
remove it from the list of required tests for backports in the
release-1.9 branch.
Signed-off-by: Travis Nielsen <tnielsen@redhat.com>
The rules for auto merging PRs from master have not been used.
Instead we follow a pattern of a maintainer deciding when is
the best time to merge the PR in case it is not ready even after
being approved.
Signed-off-by: Travis Nielsen <tnielsen@redhat.com>
With the creation of the release-1.8 branch we enable
the mergify bot to open the backport PRs automatically
based on the backport-release-1.8 label.
Signed-off-by: Travis Nielsen <tnielsen@redhat.com>
Normally, only the mergify bot should send out PR to the release
branches. All contributions should generally go in master first then be
backported. Let's warn to avoid merging PR send against a release
branch.
Signed-off-by: Sébastien Han <seb@redhat.com>
Remove the unspecific 'ceph' tag, and add a few other specific tags:
block (for block storage that is not pool-specific)
file (for file storage that is not mds-specific)
monitoring (for prometheus, etc.)
nfs (for CephNFS and nfs-ganesha)
object (for object storage that is not rgw-specific)
Signed-off-by: Blaine Gardner <blaine.gardner@redhat.com>
In Rook v1.8 the min version of K8s supported is updated to 1.16.
Users running on older versions of K8s are recommended to update
to 1.16 or newer before updating to Rook v1.8.
Signed-off-by: Travis Nielsen <tnielsen@redhat.com>
The CephSmokeSuite is becoming quite large and long, and most of the
length is now related to the object e2e tests. Separate the full object
e2e test into CephObjectSuite, and only test the object 'lite' test in
the CephSmokeSuite.
Resolves#8714
Signed-off-by: Blaine Gardner <blaine.gardner@redhat.com>
The cassandra and ceph PRs already had the label added automatically,
now the nfs PRs will also have a label added.
Signed-off-by: Travis Nielsen <tnielsen@redhat.com>
The mergify bot now has rules for backporting to the release-1.7
branch. Backporting to 1.3 is no longer needed, so we can remove
that backport rule.
Signed-off-by: Travis Nielsen <tnielsen@redhat.com>
In the release-1.6 branch, the k8s versions are different, we run
v1.20.2 where the master branch runs v1.21.0.
Signed-off-by: Sébastien Han <seb@redhat.com>
With the release of K8s 1.21.0 we now run the integration tests
on v1.21.0. To keep consistent with running master builds on five
recent releases, we keep master builds back to v1.15 and skip other
less changed versions such as v1.16 and 1.19. Jenkins builds just run
five versions, while github actions run four versions.
Signed-off-by: Travis Nielsen <tnielsen@redhat.com>
Previously forgot to add mergify rule to auto merge backports to
release-1.6. Backport PRs would still be created but not merged.
Signed-off-by: Blaine Gardner <blaine.gardner@redhat.com>
On pull request with no code changes, the canary and integration tests
won't run. This means they won't appear in the status and mergify cannot
validate them.
Signed-off-by: Sébastien Han <seb@redhat.com>
We now allow mergify to auto-merge pull requests against the master
branch under the following conditions:
* all CI tests passed
* the PR has no label 'do-not-merge'
* the PR has the label 'ready-to-merge'
* has been approved by at least one maintainer
* has not requested changes
Signed-off-by: Sébastien Han <seb@redhat.com>
With the v1.4 release we will need mergify to support
the automatic backports based on the PR label.
Signed-off-by: Travis Nielsen <tnielsen@redhat.com>
That rule posts a comment as soon as a pull request is in conflict, notifying the pull request author that they need to intervene!
Signed-off-by: Sébastien Han <seb@redhat.com>
Let's not do a rebase, but only merge. Rook is configured to refuse the
rebase and mergify fails with the following Github error:
GitHub error message: Rebase merges are not allowed on this repository.
This commit fixes the error.
Signed-off-by: Sébastien Han <seb@redhat.com>
This is round 2 attempting to add the mergify engine in Rook. In this
case, we only use the backporting and automerge features.
* auto backport: set a label on your PR and a backport PR will be
automatically created under the right branch
* auto backport PR merge: if the backport PR passes CI, mergify will
merge it.
Signed-off-by: Sébastien Han <seb@redhat.com>
Travis Nielsen
Blaine Gardner
subhamkrai
Sébastien Han
Blaine Gardner