Skip to content

ci: build and test with pixi instead of CVMFS#26

Open
olantwin wants to merge 1 commit into
mainfrom
ci/use-pixi
Open

ci: build and test with pixi instead of CVMFS#26
olantwin wants to merge 1 commit into
mainfrom
ci/use-pixi

Conversation

@olantwin
Copy link
Copy Markdown
Contributor

@olantwin olantwin commented Jun 4, 2026

Summary

  • All dependencies needed by this repo (geomodel 6.27.0 and its transitive closure: sqlite, xerces-c, nlohmann_json, eigen, geant4) are now published to the https://prefix.dev/ship channel via ship-conda-recipes, so CI no longer needs CVMFS access.
  • New pixi.toml + committed pixi.lock define the build environment (cxx-compiler, cmake, ninja, make, git, sqlite, geomodel) and three tasks: configure, build, test (the latter two depend on the former).
  • The workflow is rewritten to run on GitHub-hosted ubuntu-latest with prefix-dev/setup-pixi@v0.9.6 and a single pixi run test step — dropping the self-hosted runner, the registry.cern.ch/ship/gha-runner container, the three CVMFS volume mounts, and the LCG_109 / GeoModel 6.24.0-local2 source lines.

Test plan

  • Local: pixi install && pixi run test on a plain shell (no LCG/distrobox) — 160/160 build targets, 25/25 ctests pass in ~13 s.
  • CI: confirm the new Build and Test job runs on ubuntu-latest, installs the pixi env from the lock file, builds, and exits 0.

All dependencies are now available from the prefix.dev/ship channel
(via ship-conda-recipes), so CI no longer needs CVMFS mounts, the
CERN container, or a self-hosted runner. The new workflow runs on
ubuntu-latest with prefix-dev/setup-pixi and a single `pixi run test`
step that configures, builds, and runs ctest.
@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented Jun 4, 2026

Warning

Review limit reached

@olantwin, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 2 minutes and 29 seconds. Learn how PR review limits work.

Your organization has run out of usage credits. Purchase more in the billing tab.

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 86783a0f-a019-4fdf-baf0-80b735f07bd0

📥 Commits

Reviewing files that changed from the base of the PR and between a5bac91 and c3cf850.

⛔ Files ignored due to path filters (1)
  • pixi.lock is excluded by !**/*.lock
📒 Files selected for processing (2)
  • .github/workflows/build-test.yml
  • pixi.toml
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch ci/use-pixi

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 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