An aws
pipeline is executed on a dedicated, remote EC2 instance. The EC2 instance is created when the pipeline starts and terminated upon completion. This is useful for workloads that need to run inside a dedicated virtual machine.
Example pipeline configuration:
|
|
Windows support
AWS pipelines support windows EC2 instances as a first class citizen. Syntactically they do not differ to non Windows pipelines, but the underlying infrastructure is different.
|
|
Kind and Type
The kind and type attributes define an aws
pipeline.
|
|
Pool
The pool attribute specifies the type of machine the pipeline should run on. Please contact your system administrator for a list of machine types that are supported by your installation.
|
|
For more information about configuring pools of machines please consult the Pool file documentation.
If the runner has DRONE_ENABLE_AUTO_POOL
set to true
then the pool will be automatically configured, based on matching Platform attributes in the pipeline and the pool.yml
file.
Steps
The steps
section defines a series of shell commands. If any command returns a non-zero exit code, the pipeline fails and exits. Pipeline steps can execute inside containers as the container Entrypoint
:
|
|
Or pipeline steps can execute directly on the host machine:
|
|