otto/processors/travis-ci/example.internal.yml

42 lines
1.2 KiB
YAML

#
# This is an example of what the example.yml should convert to in terms of
# Otto's internal task execution structure
#
---
meta:
# Tasks are a discrete higher level concept, which can be mapped to resources
# for execution
tasks:
- id: 0x1
capabilities:
# "sudo false" basically means that the Travis workload doens't need a full
# virtual machine in order to operate
docker_run: true
# Operations should all exist in a single task and therefore run on a
# single colocated resource that has been allocated underneath
ops:
- id: 1
# Contexts are typically going to carry environment variables and other
# things, in the simple Travis CI example, there's really a single
# "stage" (to use Jenkins terms) in which all scripts will be executed
type: BEGINCTX
data:
name: 'Travis'
- id: 2
type: RUNPROC
data:
script: 'echo "Hello World"'
env:
# The Travis processor should set a default timeout
timeout_s: 300
- id: 3
type: RUNPROC
data:
script: 'env'
env:
timeout_s: 300
- id: 4
type: ENDCTX
data:
name: 'Travis'