Docker pipeline Configure

15 articles

About Configure

Here are the articles in this section: Triggers Configure when pipeline executions are triggered. Platform Configure the target operating system and architecture. Workspace Describes the pipeline wor…

Updated 2 years ago by Admin

Triggers

When you push code to your repository, open a pull request, or create a tag, your source control management system automatically sends a webhook to Drone which in turn triggers pipeline execution. Us…

Updated 2 years ago by Admin

Platform

Use the platform section to configure the target operating system and architecture and routes the pipeline to the appropriate runner. If unspecified, the system defaults to Linux amd64. Example Linux…

Updated 2 years ago by Admin

Workspace

Drone automatically creates a temporary volume, known as your workspace, where it clones your repository. The workspace is the current working directory for each step in your pipeline. Because the wo…

Updated 2 years ago by Admin

Cloning

Drone automatically clones your repository before executing your pipeline steps. No special configuration is required. In some cases, however, you may need to customize, override or disable the defau…

Updated 2 years ago by Admin

Steps

Pipeline steps are defined as a series of shell commands. The commands are executed inside the root directory of your git repository. The root of your git repository, also called the workspace, is sh…

Updated 2 years ago by Admin

Plugins

Plugins are docker containers that encapsulate commands, and can be shared and re-used in your pipeline. Use plugins to build and publish artifacts, send notifications, and more. Example Slack plugin…

Updated 2 years ago by Admin

Services

Drone supports launching detached service containers as part of your pipeline. The typical use case for services is when your unit tests require a running redis server, for example: 1 kind: pipeline…

Updated 2 years ago by Admin

Images

Pipeline steps are defined as a series of Docker containers. Each step must therefore define the Docker image used to create the container. 1 kind: pipeline 2 type: docker 3 name: default 4 5 steps:…

Updated 2 years ago by Admin

Parallelism

Pipeline steps are executed sequentially by default. You can optionally describe your build steps as a directed acyclic graph. In the below example we fan-out to execute the first two steps in parall…

Updated 2 years ago by Admin

Conditions

Conditions can be used to limit pipeline step execution at runtime. For example, you may want to limit step execution by branch: 1 kind: pipeline 2 type: docker 3 name: default 4 5 steps: 6 - name: b…

Updated 2 years ago by Admin

Routing

The nodes section can be used to route pipelines to groups of runners with matching labels. This can be useful when you need to route pipelines to runners with special configurations or hardware, for…

Updated 2 years ago by Admin

Volumes

Here are the articles in this section: Host Volumes Mount host volumes to access the host filesystem in your pipeline. Temporary Volumes Mount temporary volumes to share state between pipeline steps.

Updated 2 years ago by Admin

Host Volumes

Host mounts allow you to mount an absolute path on the host machine into a pipeline step. This setting is only available to trusted repositories. This setting is only available to trusted repositorie…

Updated 2 years ago by Admin

Temporary Volumes

Temporary mounts are docker volumes that are created before the pipeline starts and destroyed when the pipeline completes. This can be used to share files or folders among pipeline steps. 1 kind: pip…

Updated 2 years ago by Admin