Cloud Run jobs for batch work in GCP - Step-by-Step Execution

Process Flow - Cloud Run jobs for batch work

Define Job Container

↓

Create Cloud Run Job

↓

Trigger Job Execution

↓

Cloud Run starts container

↓

Job runs batch task

↓

Job completes and exits

↓

View logs and status

↓

Repeat or schedule next job

This flow shows how you define a container, create a Cloud Run job, run it to perform batch work, and then check results.

Execution Sample

GCP

gcloud run jobs create batch-job --image=gcr.io/my-project/my-batch-image

gcloud run jobs execute batch-job

gcloud run jobs describe batch-job

This code creates a Cloud Run job from a container image, runs it once, and then checks its status.

Process Table

Step	Action	Input/Command	Result/Output	Notes
1	Create job	gcloud run jobs create batch-job --image=gcr.io/my-project/my-batch-image	Job 'batch-job' created	Job definition saved with container image
2	Execute job	gcloud run jobs execute batch-job	Job execution started, container running	Cloud Run starts container instance
3	Job runs	Batch task inside container	Batch task processes data	Job runs to completion
4	Job completes	Container exits	Job execution finished successfully	Exit code 0 means success
5	Describe job	gcloud run jobs describe batch-job	Shows job config and last execution status	Check logs and status
6	Exit	No further commands	End of batch job lifecycle	Ready for next run or scheduling

💡 Job completes and exits after batch task finishes, no more steps.

Status Tracker

Variable	Start	After Step 1	After Step 2	After Step 4	Final
Job Definition	None	Created with image gcr.io/my-project/my-batch-image	Exists, ready to run	Execution finished successfully	Ready for next execution
Job Execution Status	None	None	Running	Succeeded	Succeeded

Key Moments - 3 Insights

Why does the job need a container image before creation?

The container image contains the batch task code and environment. Step 1 shows the job is created with the image, so Cloud Run knows what to run.

What happens if the batch task inside the container fails?

If the container exits with a non-zero code, the job execution status will show failure. Step 4 shows success, but failure would be similar with different status.

Can the job run multiple times automatically?

Cloud Run jobs run on demand or via scheduler. The flow ends after one run (Step 6), but you can schedule repeated runs externally.

Visual Quiz - 3 Questions

Look at the execution table, what is the job execution status after Step 2?

A Running

B Created

C Succeeded

D None

💡 Hint

Check the 'Job Execution Status' variable after Step 2 in variable_tracker.

At which step does the batch task inside the container complete successfully?

A Step 2

B Step 3

C Step 4

D Step 5

💡 Hint

Look at the 'Job completes' row in execution_table where the container exits.

If you want to run the job again after completion, what should you do?

A Create the job again

B Execute the job again

C Delete the job

D Change the container image

💡 Hint

Step 2 shows how to execute the job; creation is only once.

Concept Snapshot

Cloud Run jobs run batch tasks in containers.
Create a job with a container image.
Execute the job to run the batch task once.
Check status and logs after execution.
Jobs run on demand or via scheduler.
Exit code 0 means success.

Full Transcript

Cloud Run jobs let you run batch work by defining a container image with your task. You create a job using the gcloud command with the image. Then you execute the job, which starts a container instance that runs your batch task. When the task finishes, the container exits and the job completes. You can check the job's status and logs to see if it succeeded. Jobs run once per execution and can be triggered repeatedly or scheduled. This flow helps you run batch workloads easily without managing servers.