This is an interactive guide for exploring various important properties of the screwdriver.yaml configuration for projects.
You can access information about properties by hovering over the property name.
shared: environment: NODE_ENV: test settings: email: addresses: [firstname.lastname@example.org, email@example.com] statuses: [SUCCESS, FAILURE] annotations: beta.screwdriver.cd/my-cluster-annotation: my-data beta.screwdriver.cd/executor: k8s-vm beta.screwdriver.cd/cpu: HIGH beta.screwdriver.cd/ram: LOW jobs: main: requires: [~pr, ~commit, ~sd@123:main] image: node:6 steps: - init: npm install - test: npm test publish: requires: main image: node:6 steps: - publish: npm publish deploy-west: requires: publish image: node:6 environment: DEPLOY_ENV: west steps: - init: npm install - deploy: npm deploy deploy-east: requires: publish image: node:6 environment: DEPLOY_ENV: east steps: - init: npm install - deploy: npm deploy finished: requires: [deploy-west, deploy-east] image: node:6 steps: - echo: echo done ...
A single job name or array of jobs that will trigger the job to run. Jobs defined with "requires: ~pr" are started by pull-request events. Jobs defined with "requires: ~commit" are started by push events. Jobs defined with "requires: ~sd@123:main" are started by job "main" from pipeline "123". Jobs defined with "requires: [deploy-west, deploy-east] are started after "deploy-west" and "deploy-east" are both done running successfully. "Note: ~ jobs denote an OR functionality, jobs without a ~ denote join functionality.
A set of key/value pairs for environment variables that need to be set. Any configuration that is valid for a job configuration is valid in shared, but will be overridden by specific job configurations.
Configurable settings for any additional build plugins added to Screwdriver.cd.
Annotations is an optional object containing key-value pairs. These can be either pipeline or job-level specifications. Annotation key-value pairs can be completely arbitrary, as in the example, or can modify the execution of the build. Check with your screwdriver cluster admin to find what annotations are supported to modify your build execution.
Used to designate a non-default executor to run the build. Some available executors are `jenkins`, `k8s-vm`
CPU allocated for the VM if using `k8s-vm` executor. `LOW` is configured by default, and indicates 2CPU memory. `HIGH` means 6CPU.
RAM allocated for the VM if using `k8s-vm` executor. `LOW` is configured by default, and indicates 2GB memory. `HIGH` means 12GB memory.
Emails addresses to send notifications to and statuses to send notifications for.
A series of jobs that define the behavior of your builds.
This defines the Docker image used for the builds. This value should be the same as you would use for a "docker pull" command.
Defines the explicit list of commands that are executed in the build, just as if they were entered on the command line. Environment variables will be passed between steps, within the same job. Step definitions are required for all jobs. Step names cannot start with `sd-`, as those steps are reserved for Screwdriver steps. In essence, Screwdriver runs `/bin/sh` in your terminal then executes all the steps; in rare cases, different terminal/shell setups may have unexpected behavior.