Skip to content

autoscale-tests: enable Tide auto-merge - #83046

Open
ssulka wants to merge 2 commits into
openshift:mainfrom
ssulka:add-tide-autoscale-tests
Open

autoscale-tests: enable Tide auto-merge#83046
ssulka wants to merge 2 commits into
openshift:mainfrom
ssulka:add-tide-autoscale-tests

Conversation

@ssulka

@ssulka ssulka commented Aug 6, 2026

Copy link
Copy Markdown
  • Enable Tide auto-merge for openshift/autoscale-tests
  • Auto merge PRs with "lgtm" + "approved" labels

Summary by CodeRabbit

  • Enables Tide auto-merge for openshift/autoscale-tests.
  • Auto-merges pull requests with both approved and lgtm labels.
  • Excludes pull requests with configured blocking labels.
  • Enables the approve plugin for the repository.

@coderabbitai

coderabbitai Bot commented Aug 6, 2026

Copy link
Copy Markdown
Contributor

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Repository YAML (base), Central YAML (inherited)

Review profile: CHILL

Plan: Pro Plus

Run ID: ad05a047-2203-4bf2-829d-ee4d65493d10

📥 Commits

Reviewing files that changed from the base of the PR and between 272bfdb and 5112d4a.

📒 Files selected for processing (1)
  • core-services/prow/02_config/openshift/autoscale-tests/_pluginconfig.yaml

Walkthrough

Added Tide and plugin configuration for openshift/autoscale-tests. Tide requires approved and lgtm labels and excludes pull requests with blocking labels. The approve plugin is enabled.

Changes

Autoscale Tests Prow Configuration

Layer / File(s) Summary
Tide and approval plugin configuration
core-services/prow/02_config/openshift/autoscale-tests/_prowconfig.yaml, core-services/prow/02_config/openshift/autoscale-tests/_pluginconfig.yaml
Adds required approved and lgtm labels, excludes blocking label states, and enables the approve plugin.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Suggested reviewers: prucek, jmguzik

🚥 Pre-merge checks | ✅ 15
✅ Passed checks (15 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly and concisely describes enabling Tide auto-merge for autoscale-tests, which is the main change.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
Stable And Deterministic Test Names ✅ Passed The PR adds only two Prow YAML configuration files. The committed changes contain no Ginkgo declarations, test files, or dynamic test titles.
Test Structure And Quality ✅ Passed Not applicable: the PR changes only Prow YAML configuration; the target directory has no Ginkgo tests, It blocks, cluster operations, or assertions to review.
Microshift Test Compatibility ✅ Passed The PR adds only Prow YAML configuration; it adds no Ginkgo e2e tests or MicroShift-incompatible API and feature references.
Single Node Openshift (Sno) Test Compatibility ✅ Passed The PR adds only two Prow YAML configuration files; it adds no Ginkgo e2e tests or test declarations requiring SNO compatibility review.
Topology-Aware Scheduling Compatibility ✅ Passed The PR only adds Prow Tide and approve-plugin YAML; it adds no deployment, operator, controller, or pod scheduling constraints.
Ote Binary Stdout Contract ✅ Passed The checked-out PR diff adds only Prow YAML configuration and changes no OTE binary or suite setup code that could write non-JSON data to stdout.
Ipv6 And Disconnected Network Test Compatibility ✅ Passed The commit adds only a Prow plugin YAML file; it adds no Ginkgo tests, IP handling, URLs, or external connectivity requirements.
No-Weak-Crypto ✅ Passed The PR adds only Tide and approve-plugin YAML configuration. The added lines contain no MD5, SHA1, DES, RC4, Blowfish, ECB, custom crypto, or secret-comparison code.
Container-Privileges ✅ Passed The PR changes only Prow Tide and plugin YAML. No container or Kubernetes manifest contains privileged, host namespace, SYS_ADMIN, or privilege-escalation settings.
No-Sensitive-Data-In-Logs ✅ Passed The commit adds only four YAML configuration lines; scans of changed lines and the target directory found no logging calls or sensitive data.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@openshift-ci
openshift-ci Bot requested review from Prucek and jmguzik August 6, 2026 14:29
@openshift-ci

openshift-ci Bot commented Aug 6, 2026

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ssulka

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

The pull request process is described here

Details 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 Aug 6, 2026
@openshift-merge-bot openshift-merge-bot Bot added the rehearsals-ack Signifies that rehearsal jobs have been acknowledged label Aug 6, 2026
@openshift-merge-bot

Copy link
Copy Markdown
Contributor

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

Note: If this PR includes changes to step registry files (ci-operator/step-registry/) and you expected jobs to be found, try rebasing your PR onto the base branch. This helps pj-rehearse accurately detect changes when the base branch has moved forward.

Interacting with pj-rehearse

Comment: /pj-rehearse to run up to 5 rehearsals
Comment: /pj-rehearse skip to opt-out of rehearsals
Comment: /pj-rehearse {test-name}, with each test separated by a space, to run one or more specific rehearsals
Comment: /pj-rehearse more to run up to 10 rehearsals
Comment: /pj-rehearse max to run up to 25 rehearsals
Comment: /pj-rehearse auto-ack to run up to 5 rehearsals, and add the rehearsals-ack label on success
Comment: /pj-rehearse list to get an up-to-date list of affected jobs
Comment: /pj-rehearse abort to abort all active rehearsals
Comment: /pj-rehearse network-access-allowed to allow rehearsals of tests that have the restrict_network_access field set to false. This must be executed by an openshift org member who is not the PR author

Once you are satisfied with the results of the rehearsals, comment: /pj-rehearse ack to unblock merge. When the rehearsals-ack label is present on your PR, merge will no longer be blocked by rehearsals.
If you would like the rehearsals-ack label removed, comment: /pj-rehearse reject to re-block merging.

@openshift-ci

openshift-ci Bot commented Aug 6, 2026

Copy link
Copy Markdown
Contributor

@ssulka: all tests passed!

Full PR test history. Your PR dashboard.

Details

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 kubernetes-sigs/prow repository. I understand the commands that are listed here.

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. rehearsals-ack Signifies that rehearsal jobs have been acknowledged

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants