Skip to content

ci: add Lyrical as a sample (experimental) build & test distro - #17

Open
benaliabderrahmane wants to merge 1 commit into
mainfrom
ci-add-lyrical
Open

ci: add Lyrical as a sample (experimental) build & test distro#17
benaliabderrahmane wants to merge 1 commit into
mainfrom
ci-add-lyrical

Conversation

@benaliabderrahmane

Copy link
Copy Markdown
Owner

Adds the next ROS 2 release Lyrical to the build-and-test CI matrix, alongside Jazzy / Kilted / Rolling.

How

  • New matrix include entry ros_distro: lyrical flagged experimental: true.
  • Job-level continue-on-error: ${{ matrix.experimental || false }} — Lyrical builds and tests like the others but is allowed to fail, so a not-yet-stable distro never turns CI red. The three stable distros stay required.
  • Lyrical also gets the Rolling-style rosidl_buffer dependency, since it branched from Rolling after that package landed.

Scope / notes

  • Build-and-test only (ci.yml). release.yml is intentionally left unchanged — producing release artifacts for an experimental distro is premature.
  • The Lyrical job depends on ros:lyrical-ros-base and its packages being published; until then the job may show as failed-but-allowed, which is the intended 'sample' behavior.
  • Verified locally: YAML parses and the matrix expands to 4 jobs with continue-on-error true only for Lyrical.

Adds the next ROS 2 release (Lyrical) to the build-and-test matrix as an
experimental entry: it builds and tests exactly like jazzy/kilted/rolling but
is allowed to fail (job-level continue-on-error keyed on a per-entry
experimental flag), so a not-yet-stable distro never turns CI red. Lyrical also
gets the Rolling-style rosidl_buffer dependency, since it branched from Rolling
after that package landed.
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