Bitbucket Pipelines Agent Docker image for Docksal CI
A thin agent used to provision Docksal powered sandboxes on a remote Docker host.
This image(s) is part of the Docksal image library.
Docksal CI Sandboxes
For any Docksal powered project enabling Bitbucket Pipelines and dropping this file
into the project repo will enable per-branch sandbox provisioning.
URLs to sandbox environments can be found in the build logs and can also published to a desired Slack channel.
Image variants and versions
docksal/bitbucket-pipelines-agent- basic (bash, curl, git)
docksal/bitbucket-pipelines-agent:php- basic + php stack tools (composer, drush, drupal console, wp-cli, etc)
docksal/bitbucket-pipelines-agent:1.0- basic, specific version
docksal/bitbucket-pipelines-agent:1.0-php- php, specific version
Global Pipelines variables
The agent expects the following required variables to be defined.
The address of the remote Docksal host, which will be hosting sandboxes. Configure one of the other.
DOCKSAL_HOST, make sure the domain is configured as a wildcard DNS entry.
DOCKSAL_HOST_IP, the agent will use
xip.io for dynamic wildcard domain names for sandboxes.
A base64 encoded private SSH key used to access the remote Docksal host.
See Access remote hosts via SSH
tutorial for details.
A second SSH keys (base64 encoded as well), which can be used for deployments and other remote operations run directly
on the agent.
E.g. cloning/pushing a repo, running commands over SSH on a remote deployment environment.
Project level Pipelines variables
The following environment variables can be configured in the project's Pipelines settings:
The Incoming Webhook integration URL from Slack,
A public or private channel in Slack, e.g.
slack 'message' ['#channel'] ['webhook_url']
Channel and webhook url can be passed via environment variables. See below.
Incoming Webhook integration won't work for private channels, which the owner of the integration does not belong to.