Skip to content

feat: run the check jobs with pixi - #8900

Open
fstagni wants to merge 6 commits into
DIRACGrid:integrationfrom
fstagni:pixi-ci-integration
Open

fstagni wants to merge 6 commits into
DIRACGrid:integrationfrom
fstagni:pixi-ci-integration

Conversation

@fstagni

@fstagni fstagni commented Nov 16, 2026

Copy link
Copy Markdown
Contributor

Part of DIRACGrid/.github#5 (adopt pixi everywhere), stacked on #8891.

The check and check-py314 jobs of basic.yml drop setup-miniconda + environment.yml in favor of a locked pixi environment:

  • new pixi.toml: the dependency set mirrors environment.yml (conda packages from the diracgrid + conda-forge channels, plus the pip-only pieces: the DIRACGrid tornado forks and Authlib), with two environments: default (python 3.11) and py314 (python 3.14, replacing the sed-patched environment.yml workaround).
  • pixi.lock is committed: the environments are reproducible, and Renovate (via the org preset) becomes the only path for dependency changes.
  • exclude-newer = "7d" in the workspace config: per the org policy in chore: add the shared DIRACGrid Renovate config preset .github#7, the lock's release-age cooldown is enforced by the solver at lock time (Renovate's lockfile maintenance skips minimumReleaseAge).
  • the editable installs (dirac-common[testing], .[server,testing]) now run through pixi run — behavior unchanged, dependencies come from the pixi environment.
  • the pylint-py27 removal ([v9r0] chore: remove the pylint-py27 job #8894) removed the last conda-python-2.7 usage; deploy_CVMFS keeps conda for the gsissh/CVMFS tooling (system-level, unrelated to the test environments).

Verified locally: pixi lock solves both environments with exclude-newer applied. The rel-v9r0 and rel-v8r0 branches can adopt the same recipe once this is validated.

The CI check jobs now run in the locked pixi environment (pixi.toml +
committed pixi.lock), so make pixi the recommended way to create a
development environment:
- new 'Creating a development environment with pixi' section
  (install, pixi install/shell/run, the py314 environment, and the
  dependency-update policy: pixi.toml + Renovate-managed pixi.lock,
  exclude-newer cooldown)
- note in the conda section that environment.yml now mirrors pixi.toml
  and is still used by readthedocs
- generalize references to 'the conda environment' in the docs-building
  and installation-check pages
…ion workflow

- pixi.lock was still ignored by .gitignore, so it never made it into
  the branch: setup-pixi (cache: true) fails with "Failed to generate
  cache key" on every check/check-py314 job, and the environments were
  not actually locked. Remove it from .gitignore and commit the
  generated lockfile.
- the integration workflow quoted $MATRIX_ARGS, merging all KEY=VALUE
  pairs of matrix.ARGS into a single argument that
  integration_tests.py cannot split, breaking e.g.
  MYSQL_VER=mariadb:11.4.3 ES_VER=... (invalid docker reference) and
  the backward-compatibility job (mangled installation branch). Restore
  the word-splitting.
The plain $COMMAND expansion loses the single quotes around the pytest
-k expression, so pytest tried to open 'test_BaseType_Unicode' as a file
(ERROR: file or directory not found). Use eval, like the conda-based
job did.

This branch has not been deployed

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