Skip to content

(feat): update rstudio pipelines and component#69

Open
AjayJagan wants to merge 1 commit intomainfrom
onboard-rstudio-py312
Open

(feat): update rstudio pipelines and component#69
AjayJagan wants to merge 1 commit intomainfrom
onboard-rstudio-py312

Conversation

@AjayJagan
Copy link
Copy Markdown
Member

@AjayJagan AjayJagan commented Sep 25, 2025

Description

How Has This Been Tested?

Merge criteria:

  • The commits are squashed in a cohesive manner and have meaningful messages.
  • Testing instructions have been added in the PR body (for PRs involving changes that are not immediately obvious).
  • The developer has manually tested the changes and verified that the changes work

Summary by CodeRabbit

  • New Features
    • Introduced RStudio Workbench minimal images based on Python 3.12 for both CPU and CUDA variants.
  • Chores
    • Updated CI/CD pipelines to build and publish the new Python 3.12 images.
    • Refreshed image references and tags to align with the 3.12 release, including a version tag bump to 2025b-v1.36.
    • Adjusted pipeline metadata and triggers to track Python 3.12 artifacts.

@AjayJagan AjayJagan requested a review from atheo89 September 25, 2025 13:43
@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai bot commented Sep 25, 2025

Walkthrough

Updates RStudio Workbench minimal images and pipelines from Python 3.11 to 3.12 for both CPU and CUDA variants. Renames components, updates image tags, Dockerfile and build-args paths, pipeline triggers, names, labels, output tags, and service accounts. Version tag advanced in push pipelines (2025a-v1.35 → 2025b-v1.36).

Changes

Cohort / File(s) Summary
Release components (RStudio py312)
gitops/opendatahub-release-components.yaml
Renamed CPU and CUDA components from py311-c9s to py312-c9s; updated name, componentName, containerImage, and dockerfileUrl to 3.12 paths.
Pipelines — CPU (PR & Push)
pipelines/notebooks/odh-workbench-rstudio-minimal-cpu-py312-c9s-pull-request.yaml, pipelines/notebooks/odh-workbench-rstudio-minimal-cpu-py312-c9s-push.yaml
Switched triggers, labels, names, image tags, Dockerfile, and build-args from 3.11 to 3.12; updated service account; push adds additional-tag bump to 2025b-v1.36.
Pipelines — CUDA (PR & Push)
pipelines/notebooks/odh-workbench-rstudio-minimal-cuda-py312-c9s-pull-request.yaml, pipelines/notebooks/odh-workbench-rstudio-minimal-cuda-py312-c9s-push.yaml
Migrated PR and push pipelines from py311 to py312: updated regex/conditions, labels, names, output-image, Dockerfile and build-args paths, service accounts; push bumps additional-tag to 2025b-v1.36.

Sequence Diagram(s)

sequenceDiagram
  autonumber
  actor Dev as Developer
  participant GH as Git Host
  participant PaC as Pipelines-as-Code
  participant Tek as Tekton Pipeline
  participant Reg as Container Registry

  Dev->>GH: Open PR / comment trigger
  GH-->>PaC: PR event / comment
  PaC->>PaC: Match py312 PR rules (CPU/CUDA)
  PaC->>Tek: Start PR pipeline (py312)
  Tek->>Tek: Build image using rstudio/c9s-python-3.12/Dockerfile.(cpu|cuda)
  Tek->>Reg: Push image :on-pr-{{revision}}
  Tek-->>PaC: Status (success/failure)
  PaC-->>GH: Check/status update

  note over Tek,Reg: New: all references point to py312 and updated service accounts
Loading
sequenceDiagram
  autonumber
  actor Dev as Developer
  participant GH as Git Host
  participant PaC as Pipelines-as-Code
  participant Tek as Tekton Pipeline
  participant Reg as Container Registry

  Dev->>GH: Push to default branch
  GH-->>PaC: Push event
  PaC->>PaC: on-cel-expression pathChanged matches py312
  PaC->>Tek: Start push pipeline (py312)
  Tek->>Tek: Build with rstudio/c9s-python-3.12 build-args (cpu|cuda)
  Tek->>Reg: Push image tags (py312-c9s, 2025b-v1.36, ...)
  Tek-->>PaC: Status
  PaC-->>GH: Commit status

  note over PaC: Additional-tag updated: 2025b-v1.36
Loading

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Poem

Thump-thump, I hop to three-one-two,
Fresh carrots, fresher builds anew.
CPU, CUDA, tags aligned,
Docker paths neatly reassigned.
In quay we trust, with ears held high—
Merge me now, and watch me fly! 🥕🚀


📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Free

📥 Commits

Reviewing files that changed from the base of the PR and between cc2819d and f757b7f.

⛔ Files ignored due to path filters (1)
  • pipelines/components_quay_repos.csv is excluded by !**/*.csv
📒 Files selected for processing (5)
  • gitops/opendatahub-release-components.yaml (2 hunks)
  • pipelines/notebooks/odh-workbench-rstudio-minimal-cpu-py312-c9s-pull-request.yaml (2 hunks)
  • pipelines/notebooks/odh-workbench-rstudio-minimal-cpu-py312-c9s-push.yaml (2 hunks)
  • pipelines/notebooks/odh-workbench-rstudio-minimal-cuda-py312-c9s-pull-request.yaml (2 hunks)
  • pipelines/notebooks/odh-workbench-rstudio-minimal-cuda-py312-c9s-push.yaml (2 hunks)

Tip

👮 Agentic pre-merge checks are now available in preview!

Pro plan users can now enable pre-merge checks in their settings to enforce checklists before merging PRs.

  • Built-in checks – Quickly apply ready-made checks to enforce title conventions, require pull request descriptions that follow templates, validate linked issues for compliance, and more.
  • Custom agentic checks – Define your own rules using CodeRabbit’s advanced agentic capabilities to enforce organization-specific policies and workflows. For example, you can instruct CodeRabbit’s agent to verify that API documentation is updated whenever API schema files are modified in a PR. Note: Upto 5 custom checks are currently allowed during the preview period. Pricing for this feature will be announced in a few weeks.

Please see the documentation for more information.

Example:

reviews:
  pre_merge_checks:
    custom_checks:
      - name: "Undocumented Breaking Changes"
        mode: "warning"
        instructions: |
          Pass/fail criteria: All breaking changes to public APIs, CLI flags, environment variables, configuration keys, database schemas, or HTTP/GraphQL endpoints must be documented in the "Breaking Change" section of the PR description and in CHANGELOG.md. Exclude purely internal or private changes (e.g., code not exported from package entry points or explicitly marked as internal).

Please share your feedback with us on this Discord post.


Note

🎁 Summarized by CodeRabbit Free

Your organization is on the Free plan. CodeRabbit will generate a high-level summary and a walkthrough for each pull request. For a comprehensive line-by-line review, please upgrade your subscription to CodeRabbit Pro by visiting https://app.coderabbit.ai/login.

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

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant