Last Reviewed: 2023-06-08

Authenticate Terminus in a GitLab Pipeline

Learn how to authenticate Terminus in a GitLab CI pipeline without receiving errors.

Discuss in Slack

Edit this page on GitHub Report an issue with this doc

This section provides information on how to to authenticate Terminus in a GitLab CI pipeline without receiving errors and avoiding authentication rate limits.

Caching Authentication for GitLab

You can use the example script in this section as a starting point to create your own CI scripts.

This pipeline demonstrates an initial build stage which installs and authenticates Terminus, followed by a deploy_many stage with two parallel jobs which reuse the downloaded Terminus and session token.

• Uses the ubuntu:latest Docker image.
• Updates the system and installs necessary tools like PHP, cURL, and PHP libraries Terminus needs before the script stages.
• Adds the current directory to $PATH, because you will download Terminus to the current directory.
• Sets an environment variable to store the session token inside the build directory.
• Specifies that the downloaded Terminus phar and the session folder should be cached for future jobs.
• Downloads the latest release of Terminus.
• Checks that Terminus is authenticated with terminus auth:whoami.
• Runs two parallel jobs in the deploy_many stage, which both reuse the downloaded Terminus and session token.