ROX-34722: Switch to periodic konflux retest

[kurlov]

Updates the Konflux retest process to run periodically, with the goal of optimizing GitHub Actions invocations.

test: https://github.com/stackrox/test-konflux-repo/pull/5

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Central YAML (base), Organization UI (inherited)

Review profile: CHILL

Plan: Team

Run ID: a325b482-f76d-4442-9e2f-0b3b83793518

📥 Commits

Reviewing files that changed from the base of the PR and between 89bcea4 and b33cec1.

📒 Files selected for processing (1)

• .github/workflows/konflux-auto-retest.yml

Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review.

---

📝 Walkthrough

Summary by CodeRabbit

• Chores
  • Updated automated build retesting to run on a regular schedule.
  • Added an option to trigger retesting manually.
  • Improved permissions for checking build and repository status.
  • Updated the retest workflow to use the latest retest process and command.

Walkthrough

The Konflux auto-retest workflow now runs every 10 minutes or by manual dispatch. It invokes a pinned periodic retest workflow with read permissions and the /konflux-retest command.

Changes

Konflux retest automation

Layer / File(s)	Summary
Periodic retest workflow configuration .github/workflows/konflux-auto-retest.yml	The workflow replaces event triggers with a cron schedule and workflow_dispatch. It calls the pinned periodic retest workflow, adds read permissions, and passes /konflux-retest while retaining max_retries: 3.

Estimated code review effort: 2 (Simple) | ~10 minutes

Merge Risk: ⚪ Minimal · up to b33ce

This localized workflow change is merge-ready after normal checks and review; no actionable merge-blocking risk remains.

Suggested reviewers: alkmim

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly describes the main change: switching Konflux retesting to a periodic process.
Description check	✅ Passed	The description accurately explains the periodic Konflux retest update and its goal of optimizing GitHub Actions invocations.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
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.

Full details: Docstring Coverage

Explanation

No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0 files. (1 skipped: 1 unsupported.)

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch akurlov/ROX-34722-switch-to-periodic-konflux-retest

---

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

[github-actions]

/retest scanner-slim-on-push

[openshift-ci]

@github-actions[bot]: The /retest command does not accept any targets.
The following commands are available to trigger optional jobs:

/test e2e-tests

/test slim-e2e-tests

Use /test all to run all jobs.

Details

In response to this:

/retest scanner-slim-on-push

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.

[openshift-ci]

@kurlov: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/e2e-tests	b33cec1	link	false	/test e2e-tests

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.