trigger resource to your
shippable.yml gives you a way to trigger a job in your Assembly Line whenever you commit a change to that resource. This resource can be used used as an
IN input for any job.
You can create a
trigger resource by adding it to
resources: - name: <string> type: trigger version: counter: <number>
name-- should be an easy to remember text string
type-- is set to
version-- is an object which contains specific properties that apply to this resource
version: counter: 1
countershould be updated each time you want to trigger the jobs that have this resource as an input.
Used in Jobs
This resource is used as an
IN for any type of job.
Default Environment Variables
trigger is used as an
IN for a
runCI job, a set of environment variables is automatically made available that you can use in your scripts.
<NAME> is the the friendly name of the resource with all letters capitalized and all characters that are not letters, numbers or underscores removed. For example,
my-key-1 will be converted to
my_key_1 will be converted to
||The name of the resource.|
||The ID of the resource.|
||The type of the resource. In this case
||The operation of the resource; either
||The directory containing files for the resource.|
||The ID of the version of the resource being used.|
||The number of the version of the resource being used.|
Shippable Utility Functions
To make it easy to use these environment variables, the platform provides a command line utility that can be used to work with these values.
How to use these utility functions is documented here.