Skip to content

Conversation

@Randy424
Copy link
Contributor

@Randy424 Randy424 commented Nov 7, 2025

Regarding: https://issues.redhat.com/browse/ACM-26177
Update branch protections to require the correct Konflux jobs to run.

@openshift-ci openshift-ci bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Nov 7, 2025
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Nov 7, 2025

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Nov 7, 2025

@Randy424: This pull request references ACM-26177 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the task to target either version "4.21." or "openshift-4.21.", but it targets "ACM 2.16.0" instead.

In response to this:

Update branch protections to require the correct Konflux jobs to run.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Nov 7, 2025
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Nov 7, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Randy424

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Nov 7, 2025
@Randy424
Copy link
Contributor Author

Randy424 commented Nov 7, 2025

I've included the entire set of PR checks going back to release 2.9 (as opposed to just the Konflux checks...). Please let me know if we would prefer to have only the later.

Screenshot 2025-11-07 at 12 25 22 PM Screenshot 2025-11-07 at 12 25 17 PM

@openshift-ci-robot openshift-ci-robot added the rehearsals-ack Signifies that rehearsal jobs have been acknowledged label Nov 7, 2025
@openshift-ci-robot
Copy link
Contributor

[REHEARSALNOTIFIER]
@Randy424: no rehearsable tests are affected by this change

protect: true
required_pull_request_reviews:
dismiss_stale_reviews: true
required_approving_review_count: 2
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

required_approving_review_count remains at 2.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would change this to 1 since it says 2 on the PR but isn't enforced... and it always trips people up.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've had an issue open upstream on this, but no resolution in sight for it:

@Randy424
Copy link
Contributor Author

Randy424 commented Nov 7, 2025

/cc @KevinFCormier @dhaiducek

@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Nov 7, 2025

@Randy424: This pull request references ACM-26177 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the task to target either version "4.21." or "openshift-4.21.", but it targets "ACM 2.16.0" instead.

In response to this:

Regarding: https://issues.redhat.com/browse/ACM-26177
Update branch protections to require the correct Konflux jobs to run.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

Copy link
Contributor

@dhaiducek dhaiducek left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM! I've left a couple comments to consider.

dismiss_stale_reviews: true
required_approving_review_count: 2
branches:
release-2.9:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This can be removed if you want to simplify your configuration--release-2.9 and release-2.10 are no longer supported.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I agree.

Comment on lines +44 to +49
- ci/prow/check
- ci/prow/images
- ci/prow/pr-image-mirror
- ci/prow/pr-image-mirror-mce
- dco
- tide
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's fine to leave these here, but Prow will also detect its own jobs and mark them required if you want to leave them off.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, let's keep it simple and only list Konflux jobs.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@Randy424 We need to include the backplane-* branches as well, and list that they require Konflux checks. This is part of the magic - since we never configure our backplane branch to run PR checks, this will prevent people from checking in directly to a backplane branch instead of the corresponding release branch.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. rehearsals-ack Signifies that rehearsal jobs have been acknowledged

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants