Triggering your jobs

Jobs can be triggered in multiple ways, including both automated and manual triggers. For example, consider the configuration below for my-runCLI:

Triggering releases

In this configuration, my-runCLI will be triggered in one of 4 ways:

  1. my-job, which is an IN for my-runCLI finishes running and triggers it. This trigger can be switched off if needed.
  2. User commits an update to a trigger resource that is an IN for my-deploy, and hence triggers it.
  3. User right clicks on my-runCLI in the SPOG UI and clicks on Run or selects Run for my-runCLI in the Jobs list in the Grid view.

Please note that changing the params resource manually through a yml commit will not automatically trigger my-runCLI. This behavior is meant to prevent unexpected pipeline behavior, since a single commit can contains changes to several resources and cause several trigger points in the pipeline. If you want your job to be triggered when resources are manually edited in the yml, you can add a trigger input for the job and include a change to the trigger resource in the commit every time you want to automatically run your job.

Switching triggers off

You can switch off a job being triggered automatically in the section above.

jobs:
  - name: Job-3
    type: release
    steps:
      - IN: resource-2
        switch: off
      - IN: Job-1
        switch: off

As shown above, the switch: off tag can be defined for IN resources or jobs in order to turn off automatic triggering of a job when the inputs change. Note that these switches are specific to the input and should be set accordingly for each input.

When switch: off is applied to an input, the job will be displayed with a dark gray border when an update to the input would have otherwise triggered the job. Triggering the job will reset the border.

Pausing jobs

You can pause any jobs in your pipeline by right-clicking on the job, and clicking Pause Jobs. Paused jobs are never triggered automatically, irrespective of yml configuration. You can unpause a paused job to resume automatic triggers. Pause job

Triggering pipelines after CI

If you want to trigger your pipeline workflow after CI is complete, follow instructions in our Triggering pipeline jobs after CI docs