Issue #2632: chore(ci): add .travis.yml for multi-arch test execution

[jiridanek]

• Onboard onto Travis CI Partner Queue #2632

Description

How Has This Been Tested?

• https://app.travis-ci.com/github/opendatahub-io/notebooks/pull_requests

Self checklist (all need to be checked):

• Ensure that you have run make test (gmake on macOS) before asking for review
• Changes to everything except Dockerfile.konflux files should be done in odh/notebooks and automatically synced to rhds/notebooks. For Konflux-specific changes, modify Dockerfile.konflux files directly in rhds/notebooks as these require special attention in the downstream repository and flow to the upcoming RHOAI release.

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

• Chores

  • Enabled continuous integration for automated testing across multiple architectures on Linux using Python 3.12.

• Documentation

  • Established architecture decision records documenting preferred programming languages for new development and legacy code migration strategies.

[coderabbitai]

Walkthrough

Introduces Travis CI configuration for automated testing on Linux with Python 3.12 and multi-architecture support, and adds architectural decision record documenting language preferences (Python, Go, TypeScript) for new development and legacy Bash script migration.

Changes

Cohort / File(s)	Summary
CI/CD Configuration .travis.yml	New Travis CI configuration enabling automated testing on Linux with Python 3.12, uv-based dependency management, and venv setup with lock file synchronization
Architecture Decision docs/architecture/decisions/0003-prefer-python-go-and-typescript-in-this-order.md	New ADR documenting decision to prioritize Python, Go, and TypeScript for new development and gradual migration of legacy Bash scripts, including context, rationale, and consequences

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

• .travis.yml: Verify Python version, uv command syntax, and test target alignment with project structure
• Architecture decision file: Confirm decision status, context rationale, and language ordering alignment with team consensus

Pre-merge checks and finishing touches

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The PR description is largely incomplete and does not adequately follow the required template. While it references the related issue (#2632), the critical sections 'Description' and 'How Has This Been Tested?' are empty placeholders with no details provided. Additionally, all items in both the self checklist and merge criteria checklist remain unchecked, indicating the developer has not confirmed running tests, checking development location guidelines, or verifying commit quality and testing.	The author must fill in the Description section with details about the changes made (Travis CI configuration and architecture decision document), complete the 'How Has This Been Tested?' section with specific testing steps and results, and check off the appropriate boxes in both checklists. Specifically, they should document how they verified the Travis CI configuration works correctly and confirm they have run make test before requesting review.

✅ Passed checks (1 passed)

Check name	Status	Explanation
Title check	✅ Passed	The pull request title 'Issue #2632: chore(ci): add .travis.yml for multi-arch test execution' directly and specifically describes the main change in the changeset. It clearly indicates that the PR adds a Travis CI configuration file for multi-architecture test execution, which matches the primary content of the changes (the new .travis.yml file). The title is concise, specific, and provides meaningful information about the primary change.

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

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

• X
• Mastodon
• Reddit
• LinkedIn

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

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (2)

.travis.yml (1)

11-14: Consider adding dependency caching for faster builds.

Install phases that download and install dependencies on every build can be slow. Travis CI supports caching of pip/Python dependencies. Consider adding a cache section to speed up repeated builds:

cache:
  pip: true
  directories:
    - .venv

This is optional but recommended for faster CI feedback loops.

docs/architecture/decisions/0003-prefer-python-go-and-typescript-in-this-order.md (1)

15-15: Address static analysis style issues.

Three style/grammar improvements flagged by LanguageTool:

1. Line 15: Replace "in preference to" with "over" for conciseness.
2. Line 46: Add hyphen to "second-class citizen" (compound adjective).
3. Line 48: Replace "in preference to" with "over" for consistency and conciseness.

Apply this diff:

-Use these languages in preference to Bash.
+Use these languages over Bash.

-... language bindings are a bit of a second class citizen.
+... language bindings are a bit of a second-class citizen.

-We will consider using full-stack TypeScript in preference to having either a Python or Go backend to a TypeScript frontend.
+We will consider using full-stack TypeScript over having either a Python or Go backend to a TypeScript frontend.

Also applies to: 46-46, 48-48

📜 Review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 731c89f and 20c563b.

📒 Files selected for processing (2)

• .travis.yml (1 hunks)
• docs/architecture/decisions/0003-prefer-python-go-and-typescript-in-this-order.md (1 hunks)

🧰 Additional context used

🪛 LanguageTool

docs/architecture/decisions/0003-prefer-python-go-and-typescript-in-this-order.md

[style] ~15-~15: ‘in preference to’ might be wordy. Consider a shorter alternative.
Context: ...degree) TypeScript. Use these languages in preference to Bash. ## Decision The team has agreed...

(EN_WORDINESS_PREMIUM_IN_PREFERENCE_TO)

---

[grammar] ~46-~46: Use a hyphen to join words.
Context: ... language bindings are a bit of a second class citizen. We will consider using f...

(QB_NEW_EN_HYPHEN)

---

[style] ~48-~48: ‘in preference to’ might be wordy. Consider a shorter alternative.
Context: ...ll consider using full-stack TypeScript in preference to having either a Python or Go backend to...

(EN_WORDINESS_PREMIUM_IN_PREFERENCE_TO)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)

• GitHub Check: code-static-analysis

🔇 Additional comments (3)

.travis.yml (2)

1-5: Verify Travis CI is still actively maintained and appropriate for this project.

Travis CI has undergone significant changes, including workforce reductions and sustainability challenges. As of 2024-2025, confirm that Travis CI aligns with your CI/CD strategy and is the appropriate choice compared to GitHub Actions (which integrates natively with GitHub) or other maintained alternatives.

Additionally, document the rationale for the multi-architecture build targets (ppc64le, s390x) and whether these architectures align with your deployment requirements. Are these architectures tested regularly, and is there a business need to support them?

---

11-14: Clarify venv activation and uv command usage.

The installation phase creates a virtual environment with uv venv but does not explicitly activate it. Verify that uv sync --locked operates correctly in the Travis CI environment without an explicit source .venv/bin/activate step. Additionally, ensure that subsequent invocations of make test use the correct Python from the virtual environment (either by PATH manipulation or by uv's automatic context handling).

Document this in a comment or verify it works as intended.

docs/architecture/decisions/0003-prefer-python-go-and-typescript-in-this-order.md (1)

1-54: ADR structure and content are well-documented.

The ADR follows good practices with clear sections, explicit rationale, and practical guidance. The decision to prefer Python, Go, and TypeScript aligns well with the Travis CI addition in .travis.yml (Python 3.12 focus). The context regarding Bash script maintenance challenges is compelling, and the per-language commentary is helpful.

Minor note: Ensure this ADR is discoverable in your documentation index or decision log so the team regularly references it during code reviews and development decisions.

[daniellutz]

looking forward to see how TravisCI will still go nowadays

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: daniellutz

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:

• OWNERS [daniellutz]

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

[openshift-ci-robot]

/retest-required

Remaining retests: 0 against base HEAD 731c89f and 2 for PR HEAD 20c563b in total

[openshift-ci-robot]

/retest-required

Remaining retests: 0 against base HEAD 7c7e9a7 and 1 for PR HEAD 20c563b in total

[openshift-ci-robot]

/retest-required

Remaining retests: 0 against base HEAD f738fa7 and 0 for PR HEAD 20c563b in total

[openshift-ci]

@jiridanek: 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/images	20c563b	link	true	/test images

Full PR test history. Your PR dashboard.

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-ci-robot]

/hold

Revision 20c563b was retested 3 times: holding