feat: test trunk-based workflow in an isolated project

Eugene Harold Krabsrequested to merge
feat/1-workflow-integration into main

Plan

  1. Add the requested version/namespace inputs and catalog component includes.
  2. Assert real default-branch workflow settings after the configuration job.
  3. Connect the isolated project to CI Tools integration testing.

Acceptance criteria

  • Defaults are main and xrow-public/ci-tools.
  • Common, workflow-trunkbased and API-based settings checks are included.
  • Catalog CI_JOB_TOKEN access is allowlisted.
  • GitLab CI lint passes.
  • Required MR CI succeeds.
  • Default-branch integration verifies protected main, fast-forward merges, mandatory successful pipelines/discussions and squash policy.

Closes #1 (closed).

Related to xrow-public/ci-tools#417 (closed). Existing mocked catalog regressions stay in the catalog. Default-branch settings checks deliberately do not mutate the catalog project.

Closes #1 (closed)

Verification

MR pipeline: https://gitlab.com/xrow-public/test-projects/workflow-trunkbased/-/pipelines/2981629423

Complete default-branch proof (configuration, settings assertions and release): https://gitlab.com/xrow-public/test-projects/workflow-trunkbased/-/pipelines/2981644815. The original CI config path was restored after compilation.

Edited by Eugene Harold Krabs

Merge request reports