You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
"- `requires`: Jobs are run in parallel by default, so you must explicitly require any dependencies by their job name.\n"+
51
51
"- `name`: can be used to invoke reusable jobs across any number of workflows. Using the `name` key ensures numbers are not appended to your job name (i.e. sayhello-1 , sayhello-2, etc.). The name you assign to the name key needs to be unique, otherwise the numbers will still be appended to the job name.\n"+
52
52
"- `context`: Jobs may be configured to use global environment variables set for an organization, see the Contexts document for adding a context in the application settings.\n"+
53
-
"- `type`: A job may have a type of `approval` indicating it must be manually approved before downstream jobs may proceed.\n"+
53
+
"- `type`: Job type, can be build, release, no-op, or approval. If not specified, defaults to build.\n"+
54
54
"- `filters`: Job Filters can have the key branches or tags.+\n"+
55
55
"- `matrix` : requires config `2.1`. The `matrix` stanza allows you to run a parameterized job multiple times with different arguments.\n"+
56
56
"- `pre-steps` and `post-steps`: requires config `2.1`. Steps under `pre-steps` are executed before any of the other steps in the job. The steps under `post-steps` are executed after all of the other steps.\n"
0 commit comments