Same instance only#
This page tells you where Preflight components can run, and what to do when your app is not on the right instance. Read it before you add an include if your app lives on a different GitLab than this project.
The rule#
Components work only inside the GitLab instance that hosts this project.
Every include in this manual takes the form component: $CI_SERVER_FQDN/enterprise-apps/preflight/<name>@<full commit SHA>. The path is built from $CI_SERVER_FQDN, the instance the pipeline runs on, so the component must be resolvable on that same instance.
What that means for your app#
- Your app must live on the same GitLab instance that hosts this project; if it does not, the components cannot run here.
- git.wayne.edu now has an instance runner, and the stack's CI runs on it. Every product in the stack still strongly recommends a git.wayne.edu instance runner, so that capacity stays there. See Strongly recommended: a git.wayne.edu instance runner.
- A package that is also mirrored to
github.com/waynestatecannot include the components there, because GitHub is not a GitLab instance at all. For those mirrors, Preflight ships a reusable GitHub Actions workflow that runs the same checks: the package'scomposer ciscript on each supported PHP version, plus a Composer audit. See GitHub mirrors.
Mirroring is the only exception#
The one way to use the components on another GitLab instance is mirroring: mirror this project to that instance, so the components live there too. Everything else in this manual assumes the app and the components share an instance.
Related#
- GitHub mirrors: the reusable GitHub Actions workflow for packages mirrored to
github.com/waynestate. - Strongly recommended: a git.wayne.edu instance runner: where the stack's CI runs, and why the recommendation stays.
- When the components run: the
workflow:rulesblock that belongs in the app's own file.