CI pipelines
Pipelines: the short version
One token per pipeline, kept in the pipeline secrets, and the same commands as your laptop.
- Make a token just for the pipeline, named after it, like
storefront-ci. Ask an admin to place it in the application and environment it builds for. - Save it as a secret in your CI system, for example
REPO_TOKEN. - Use the same setup commands as on your laptop, reading the token from that secret.
- Use
npm ci,pip install -r requirements.txtor pinned image tags, so builds install exactly what you tested.
Tip
When a pipeline install is blocked, the error line in the build log says what and why. The package is often already waiting in Requests for an approver.