• Fisher documentation
  • Next page: Changelog
  • Previous page
  • Source code
  • Report an issue
  • Home page
  • Introduction
  • Why you should use Fisher
  • Installing Fisher
  • Tutorials
  • Automatic deploy from GitHub
  • Send emails when scripts fails
  • Features
  • Live reloading
  • Monitoring with status hooks
  • Monitoring with the health endpoint
  • Rate limits
  • Third-party providers
  • Documentation
  • The configuration file
  • Configuration comments
  • Scripts execution context
  • Supported providers
  • Standalone provider
  • GitHub provider
  • GitLab provider
  • Other information
  • Changelog

The GitLab provider

The GitLab provider allows you to integrate with GitLab, a code hosting platform also available self-hosted. GitLab supports a few webhooks, mostly related to its main features.

The provider perform some consistency checks on the incoming webhooks, to ensure they come from a GitLab instance. It can also check if the secret key sent by GitLab along with the webhook matches the one configured in the script (using configuration comments), rejecting invalid requests.

Configuration

## Fisher-GitLab: {"secret": "secret key", "events": ["Push", "Issue"]}

The provider is configured with a configuration comment, and supports the following keys:

  • secret: the secret key used to sign webhooks
  • events: a whitelist of GitLab events you want to accept

Environment varialbles

The provider sets the following environment variables during the execution of the script:

  • FISHER_GITLAB_EVENT: the name of the event of this webhook
  • Created by Pietro Albini