Initial conda configurations import (pixi testing on github actions)

.github/workflows/ci-pixi.yaml

@@ -0,0 +1,23 @@
+name: Conda env testing
+
+on:
+  pull_request:
+  push:
+    paths:
+      - 'conda/envs/legacy/**'
+
+jobs:
+  legacy_pixi_test:
+    runs-on: ubuntu-latest
+    name: Legacy Pixi
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v4
+        with:
+          fetch-depth: 0
+      - name: Install pixi
+        uses: prefix-dev/setup-pixi@ba3bb36eb2066252b2363392b7739741bb777659  # v0.8.1
+        with:
+          locked: true
+          cache: false  # 10Gb limit might be too low for caching
+          manifest-path: conda/envs/legacy/pixi.toml

conda/README.md

@@ -0,0 +1,37 @@
+# Conda configurations and tools for Gazebo
+
+This repository hosts the Conda related configurations and files used
+by the Gazebo project.
+
+> [!IMPORTANT]
+> Currently the Gazebo project is only using Conda for supporting the
+> build on Windows. The builds or Conda packages can perfectly work
+> on different platforms but the core team is not actively testing
+> them.
+
+## The envs/ (environments) directory
+
+The environments directory hosts the Conda environments and Pixi projects
+configurations used for different combinations of Gazebo distributions.
+
+## Create environments with Pixi
+
+[Pixi](https://prefix.dev/) can be used to recreate a Gazebo development
+environment. Navigate to the right subdirectory under `envs/` where the
+`pixi.lock` and `pixi.toml` files are located and run:
+
+```bash
+pixi install --locked
+```
+
+## Environments available
+
+### The legacy environment
+
+The legacy environment has the goal of replacing the previous vcpkg
+installation used by the Gazebo Buildfarm for testing Garden, Harmonic
+and Ionic. The software versions chosen are mostly based on the Ubuntu
+Jammy versions.
+
+The legacy enviroment is locked to use always the same exact set of
+version dependencies.