Spinnaker Stage Run Job: Difference between revisions
Jump to navigation
Jump to search
Line 5: | Line 5: | ||
* [[Spinnaker_Concepts#Run_Job|Spinnaker Concepts]] | * [[Spinnaker_Concepts#Run_Job|Spinnaker Concepts]] | ||
* [[Spinnaker Running an Arbitrary Script as Kubernetes Job#Overview|Running an Arbitrary Script as Kubernetes Job]] | * [[Spinnaker Running an Arbitrary Script as Kubernetes Job#Overview|Running an Arbitrary Script as Kubernetes Job]] | ||
* [[Spinnaker_Concepts#Running_Arbitrary_Functionality_in_a_Pipeline_Stage|Running Arbitrary Functionality in a Pipeline Stage]] | |||
=Overview= | =Overview= |
Revision as of 23:22, 29 April 2022
External
Internal
- Spinnaker Concepts
- Running an Arbitrary Script as Kubernetes Job
- Running Arbitrary Functionality in a Pipeline Stage
Overview
This stage runs a job in the form of an arbitrary container. A docker registry must be setup so that Spinnaker can access the images to run. An alternative is to run a Kubernetes Job.
Also see: