Jobs are one-off tasks triggered by a user or via a deploy hook.
On the Jobs page you can view a list of all jobs in the project.
On the Jobs page, select Create job.
You can select the container registry, image and tag, mount files into the container and select memory and CPU allocation.
Additionally you can specify static environment variables, and a set of environment variables to act as an overridable preset for job runs. See Job parameters.
You can also set a timeout to job runs, and enable auto-deletion of finished job runs after a certain amount of time.
Creating an job does not immediately trigger it. See Triggering a job below.
On the Run tab you can manually trigger the job.
You can also use a deploy hook to trigger a job. See Deploy hooks.
Under Configuration tab, it is possible to choose a set of environment variables under Default parameters.
Variables defined in Default parameters will appear on the Run-tab, and their values can be customized for each run.
Individual job runs can be deleted in the UI by selecting Delete run.
As mentioned above in Creating jobs, you can also configure an auto-deletion time threshold for each job.
Behind the scenes the job is stored as a Kubernetes Secret.
When the job is triggered, Shipmight deploys the job as a Helm release. The Job-manifest in the chart contains the
"helm.sh/resource-policy": keep annotation. Therefore, when the release is upgraded (triggered again), old Jobs remain in the cluster. They can be deleted by the user via the UI, or they can be cleaned up by auto-deletion if the user has set a time under job configuration in the UI.