Spinnaker Stage Run Job: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
| Line 4: | Line 4: | ||
=Internal= | =Internal= | ||
* [[Spinnaker_Concepts#Run_Job|Spinnaker Concepts]] | * [[Spinnaker_Concepts#Run_Job|Spinnaker Concepts]] | ||
* [[Spinnaker_Concepts#Running_Arbitrary_Functionality_in_a_Pipeline_Stage|Running Arbitrary Functionality in a Pipeline Stage]] | * [[Spinnaker_Concepts#Running_Arbitrary_Functionality_in_a_Pipeline_Stage|Running Arbitrary Functionality in a Pipeline Stage]] | ||
| Line 10: | Line 9: | ||
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. | 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: | Also see: | ||
{{Internal|Spinnaker_Concepts#Running_Arbitrary_Functionality_in_a_Pipeline_Stage|Running Arbitrary Functionality in a Pipeline Stage}} | |||
Latest revision as of 04:35, 30 April 2022
External
Internal
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: