Skip to content

CNTRLPLANE-2650: docs: add AI-assisted CI jobs documentation - #7598

Merged
openshift-merge-bot[bot] merged 2 commits into
openshift:mainfrom
bryan-cox:CNTRLPLANE-2650
Feb 2, 2026
Merged

openshift-merge-bot[bot] merged 2 commits into
openshift:mainfrom
bryan-cox:CNTRLPLANE-2650

Conversation

@bryan-cox

Copy link
Copy Markdown
Member

What this PR does / why we need it:

Adds comprehensive documentation for the HyperShift AI-assisted Jira-solve and address-review Claude prow CI jobs to meet compliance requirements and provide user guidance.

The documentation includes:

  • Human review disclaimer and responsible use guidelines link
  • Jira Agent (periodic-jira-agent) workflow and data flow diagram
  • Review Agent (periodic-review-agent) workflow and data flow diagram
  • User guide for submitting issues and viewing output
  • Limitations, support, and monitoring information
  • Data security and authentication details

Which issue(s) this PR fixes:

Fixes https://issues.redhat.com/browse/CNTRLPLANE-2650

Special notes for your reviewer:

  • Documentation covers both jobs added in openshift/release#70147 and openshift/release#73642
  • Mermaid diagrams render correctly with the existing mkdocs-mermaid2 plugin
  • All JIRA acceptance criteria have been addressed (human review disclaimer, responsible use link, PR review requirement, usage scope, data flow diagrams, monitoring process, support/feedback info)

Checklist:

  • Subject and description added to both, commit and PR.
  • Relevant issues have been referenced.
  • This change includes docs.
  • This change includes unit tests.

🤖 Generated with Claude Code

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Jan 28, 2026
@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 Jan 28, 2026
@openshift-ci

openshift-ci Bot commented Jan 28, 2026

Copy link
Copy Markdown
Contributor

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

openshift-ci-robot commented Jan 28, 2026

Copy link
Copy Markdown

@bryan-cox: This pull request references CNTRLPLANE-2650 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 the "4.22.0" version, but no target version was set.

Details

In response to this:

What this PR does / why we need it:

Adds comprehensive documentation for the HyperShift AI-assisted Jira-solve and address-review Claude prow CI jobs to meet compliance requirements and provide user guidance.

The documentation includes:

  • Human review disclaimer and responsible use guidelines link
  • Jira Agent (periodic-jira-agent) workflow and data flow diagram
  • Review Agent (periodic-review-agent) workflow and data flow diagram
  • User guide for submitting issues and viewing output
  • Limitations, support, and monitoring information
  • Data security and authentication details

Which issue(s) this PR fixes:

Fixes https://issues.redhat.com/browse/CNTRLPLANE-2650

Special notes for your reviewer:

  • Documentation covers both jobs added in openshift/release#70147 and openshift/release#73642
  • Mermaid diagrams render correctly with the existing mkdocs-mermaid2 plugin
  • All JIRA acceptance criteria have been addressed (human review disclaimer, responsible use link, PR review requirement, usage scope, data flow diagrams, monitoring process, support/feedback info)

Checklist:

  • Subject and description added to both, commit and PR.
  • Relevant issues have been referenced.
  • This change includes docs.
  • This change includes unit tests.

🤖 Generated with Claude Code

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.

@coderabbitai

coderabbitai Bot commented Jan 28, 2026

Copy link
Copy Markdown
Contributor

Walkthrough

Adds a new AI-assisted CI jobs how-to page and navigation entry; substantially expands the reference/aggregated docs with many platform-specific guides, API schema additions, and new resource/type definitions.

Changes

Cohort / File(s) Summary
AI-Assisted CI Docs
docs/content/how-to/ci/ai-assisted-ci-jobs.md
New how-to describing Claude Code–powered CI jobs (periodic-jira-agent, periodic-review-agent, review-agent-single-pr): schedules, JQL, max items, data flows, config variables, usage steps (submit/view/reprocess/trigger), monitoring, limitations, security, and support.
Docs Navigation
docs/mkdocs.yml
Adds CI navigation entry "AI-Assisted CI Jobs" linking to the new documentation page.
Reference / Aggregated Docs
docs/content/reference/aggregated-docs.md
Large expansion adding platform-specific procedures, troubleshooting, sample manifests, and extensive API/schema documentation (new and extended types, enums, and fields for HostedCluster, HostedControlPlane, NodePool, platform specs for AWS/Azure/GCP/OpenStack/PowerVS/KubeVirt, publishing strategies, secret/encryption specs, and related status/validation notes).

Estimated code review effort

🎯 5 (Critical) | ⏱️ ~120 minutes


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

@openshift-ci openshift-ci Bot added do-not-merge/needs-area area/documentation Indicates the PR includes changes for documentation labels Jan 28, 2026
@openshift-ci

openshift-ci Bot commented Jan 28, 2026

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: bryan-cox

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

@bryan-cox
bryan-cox marked this pull request as ready for review January 28, 2026 14:50
@openshift-ci openshift-ci Bot added approved Indicates a PR has been approved by an approver from all required OWNERS files. and removed do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. do-not-merge/needs-area labels Jan 28, 2026
@openshift-ci
openshift-ci Bot requested review from csrwng and devguyio January 28, 2026 14:53

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Actionable comments posted: 1

🤖 Fix all issues with AI agents
In `@docs/content/how-to/ci/ai-assisted-ci-jobs.md`:
- Around line 245-247: The fenced code block containing the command "/test
review-agent-single-pr" lacks a language specifier which triggers MD040; update
the fenced block around "/test review-agent-single-pr" to include an explicit
language (e.g., add "text" after the opening backticks) so the block reads like
```text ... ``` to satisfy markdownlint and improve readability.

Comment on lines +245 to +247
```
/test review-agent-single-pr
```

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

⚠️ Potential issue | 🟡 Minor

Add a language to the fenced code block to satisfy MD040.
This avoids markdownlint warnings and improves readability.

✅ Suggested fix
-```
-/test review-agent-single-pr
-```
+```text
+/test review-agent-single-pr
+```
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
```
/test review-agent-single-pr
```
🧰 Tools
🪛 markdownlint-cli2 (0.18.1)

245-245: Fenced code blocks should have a language specified

(MD040, fenced-code-language)

🤖 Prompt for AI Agents
In `@docs/content/how-to/ci/ai-assisted-ci-jobs.md` around lines 245 - 247, The
fenced code block containing the command "/test review-agent-single-pr" lacks a
language specifier which triggers MD040; update the fenced block around "/test
review-agent-single-pr" to include an explicit language (e.g., add "text" after
the opening backticks) so the block reads like ```text ... ``` to satisfy
markdownlint and improve readability.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Actionable comments posted: 1

🤖 Fix all issues with AI agents
In `@docs/content/reference/aggregated-docs.md`:
- Around line 9649-9650: Update the "Responsible Use" note so the referenced
phrase "Guidelines on Responsible Use of AI Code Assistants" becomes a markdown
link to the actual guidelines document; edit the block starting with the info
admonition title "Responsible Use" and replace the plain text with a
link-formatted reference (e.g., [Guidelines on Responsible Use of AI Code
Assistants](URL)) pointing to the canonical guidelines URL so users can click
through directly.
🧹 Nitpick comments (2)
docs/content/reference/aggregated-docs.md (2)

9697-9703: Use correct language identifier for JQL query.

The code block is marked as sql, but this is actually JQL (Jira Query Language), which has different syntax. Use jql or text as the language identifier instead.

📝 Suggested correction
-```sql
+```jql
 project in (OCPBUGS, CNTRLPLANE)
   AND resolution = Unresolved
   AND status in (New, "To Do")
   AND labels = issue-for-agent
   AND labels != agent-processed
</details>

---

`9886-9888`: **Add language identifier to code block.**

The code block is missing a language identifier, which affects rendering and consistency.


<details>
<summary>📝 Suggested fix</summary>

```diff
-```
+```bash
 /test review-agent-single-pr
</details>

As per coding guidelines: Static analysis tool markdownlint-cli2 flagged this as MD040 violation (fenced-code-language).

</blockquote></details>

</blockquote></details>

<!-- This is an auto-generated comment by CodeRabbit for review status -->

Comment on lines +9649 to +9650
!!! info "Responsible Use"
Please review the Guidelines on Responsible Use of AI Code Assistants before using these tools.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

⚠️ Potential issue | 🟡 Minor

Add link to the referenced guidelines document.

The documentation references "Guidelines on Responsible Use of AI Code Assistants" but doesn't provide a link, making it difficult for users to access this important resource.

🔗 Suggested fix to add the link

If the guidelines document is available, please add a markdown link. For example:

 !!! info "Responsible Use"
-    Please review the Guidelines on Responsible Use of AI Code Assistants before using these tools.
+    Please review the [Guidelines on Responsible Use of AI Code Assistants](URL_TO_GUIDELINES) before using these tools.
🤖 Prompt for AI Agents
In `@docs/content/reference/aggregated-docs.md` around lines 9649 - 9650, Update
the "Responsible Use" note so the referenced phrase "Guidelines on Responsible
Use of AI Code Assistants" becomes a markdown link to the actual guidelines
document; edit the block starting with the info admonition title "Responsible
Use" and replace the plain text with a link-formatted reference (e.g.,
[Guidelines on Responsible Use of AI Code Assistants](URL)) pointing to the
canonical guidelines URL so users can click through directly.

bryan-cox and others added 2 commits January 28, 2026 11:21
Add comprehensive documentation for the HyperShift AI-assisted Jira-solve
and address-review Claude prow CI jobs to meet compliance requirements
and provide user guidance.

The documentation includes:
- Human review disclaimer and responsible use guidelines
- Jira Agent (periodic-jira-agent) workflow and data flow
- Review Agent (periodic-review-agent) workflow and data flow
- User guide for submitting issues and viewing output
- Limitations, support, and monitoring information
- Data flow diagrams using mermaid

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Add detailed documentation for the review agent's comment analysis logic:
- What counts as an unresolved review thread
- Author authorization (openshift org, OWNERS file, approved bots)
- Response rules (one response per feedback, code changes only when requested)
- Update max agentic turns to 100 per PR

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Actionable comments posted: 1

🤖 Fix all issues with AI agents
In `@docs/content/reference/aggregated-docs.md`:
- Around line 9697-9703: The fenced SQL block and the `/test
review-agent-single-pr` command block violate markdownlint rules MD046/MD040;
fix by either converting the fenced SQL block (project in (OCPBUGS, CNTRLPLANE)
...) to an indented code block or wrap the fenced block with a local lint
disable/enable comment (<!-- markdownlint-disable MD046 MD040 --> ... <!--
markdownlint-enable MD046 MD040 -->) and add an explicit language for the
command block (e.g., ```bash) around `/test review-agent-single-pr`; apply the
same change pattern for the other occurrences referenced (the blocks at
9707-9736, 9816-9844, 9886-9888) so each fenced block has a language and any
MD046/MD040 violations are locally disabled/enabled.

Comment on lines +9697 to +9703
```sql
project in (OCPBUGS, CNTRLPLANE)
AND resolution = Unresolved
AND status in (New, "To Do")
AND labels = issue-for-agent
AND labels != agent-processed
```

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

⚠️ Potential issue | 🟡 Minor

Fix markdownlint MD046/MD040 violations for code blocks.

markdownlint expects indented blocks (MD046) and a language for fenced blocks (MD040). Either convert these to indented blocks or wrap fenced blocks with a local markdownlint disable; additionally, add a language for the /test command block.

✅ Minimal fix example (language + lint disable)
+<!-- markdownlint-disable MD046 -->
 ```mermaid
 flowchart TD
     subgraph "Prow CI Environment"
         A[Periodic Job Trigger<br/>Weekly Monday 8:30 UTC] --> B[Setup Step]
         B --> C[Process Step]
 ...

+


```diff
-```
+/```bash
 /test review-agent-single-pr
</details>



Also applies to: 9707-9736, 9816-9844, 9886-9888

<details>
<summary>🧰 Tools</summary>

<details>
<summary>🪛 markdownlint-cli2 (0.18.1)</summary>

9697-9697: Code block style
Expected: indented; Actual: fenced

(MD046, code-block-style)

</details>

</details>

<details>
<summary>🤖 Prompt for AI Agents</summary>

In @docs/content/reference/aggregated-docs.md around lines 9697 - 9703, The
fenced SQL block and the /test review-agent-single-pr command block violate
markdownlint rules MD046/MD040; fix by either converting the fenced SQL block
(project in (OCPBUGS, CNTRLPLANE) ...) to an indented code block or wrap the
fenced block with a local lint disable/enable comment ( ... ) and add an
explicit language for the command block (e.g., ```bash) around /test review-agent-single-pr; apply the same change pattern for the other occurrences
referenced (the blocks at 9707-9736, 9816-9844, 9886-9888) so each fenced block
has a language and any MD046/MD040 violations are locally disabled/enabled.


</details>

<!-- fingerprinting:phantom:triton:eagle -->

<!-- This is an auto-generated comment by CodeRabbit -->

@celebdor

celebdor commented Feb 2, 2026

Copy link
Copy Markdown
Collaborator

/lgtm

@celebdor

celebdor commented Feb 2, 2026

Copy link
Copy Markdown
Collaborator

/verified by rehearsing

@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Feb 2, 2026
@openshift-ci-robot

Copy link
Copy Markdown

@celebdor: This PR has been marked as verified by rehearsing.

Details

In response to this:

/verified by rehearsing

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 openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Feb 2, 2026
@openshift-ci

openshift-ci Bot commented Feb 2, 2026

Copy link
Copy Markdown
Contributor

@bryan-cox: 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.

@openshift-merge-bot
openshift-merge-bot Bot merged commit b746f4e into openshift:main Feb 2, 2026
10 checks passed
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. area/documentation Indicates the PR includes changes for documentation jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged. verified Signifies that the PR passed pre-merge verification criteria

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants