[CDS-105245] Added Google Cloud Run Job step details #8919
Conversation
vishal-av
requested review from
krishi0408,
SushrutHarness,
pranaykaikini and
prasadsatamharness
as code owners
|
|
|
Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://6762d165dd150200819e4d5d--harness-developer.netlify.app |
| Here's a high-level summary of the setup steps: | ||
| A **Google Cloud Run Job**, on the other hand, is a one-off, task-based execution model where the container runs to completion. Jobs are used for batch processing, scheduled tasks, and background workloads that don't require continuous execution. While Services remain active to handle incoming requests, Jobs are designed to start, run a task, and then exit once complete. | ||
|
|
||
| ## Google CLoud Run Service |
There was a problem hiding this comment.
| ## Google CLoud Run Service | |
| ## Google Cloud Run Service |
| @@ -105,6 +109,57 @@ Here's a high-level summary of the setup steps: | |||
|
|
|||
| 10. Select **Save**, and then run the pipeline. | |||
|
|
|||
| ## Google CLoud Run Job | |||
There was a problem hiding this comment.
| ## Google CLoud Run Job | |
| ## Google Cloud Run Job |
|
|
||
|  | ||
|
|
||
| **Container Configuration** |
There was a problem hiding this comment.
Consider making these headers with ### so that its more visually distinct.
|
|
||
| For Container Configuration, you need to set up a connector to the container registry. | ||
|
|
||
| For Container Registry, create or select a Docker connector to access the container registry. |
There was a problem hiding this comment.
If you're referencing a UI element, it should be bold. In this case Container Registry and Container Configuration
|
|
||
| **Deploy and Execute Steps** | ||
|
|
||
| The **Deploy Step** uses the `gcloud run jobs replace` command to apply the YAML manifest provided by the user. |
There was a problem hiding this comment.
We do not have separate deploy & execute steps here. The same job step first runs the replace command and then the execute command.
|
|
||
| For Container Registry, create or select a Docker connector to access the container registry. | ||
| For Container Configuration, use the following public Docker image: | ||
| - [`harness/google-cloud-run-plugin:1.0.0-linux-amd64`](https://hub.docker.com/layers/harness/google-cloud-run-plugin/1.0.0-linux-amd64/images/sha256-2ad0c6d434673e56df47f1014c397d2bbc8248f8e76b5bbd48965f116f4843f2?context=explore). |
There was a problem hiding this comment.
We can add 1.0.1 tag. I had made some fixes for job in the latest release.
vishal-av
added
the
Blocked / On hold
Thanks for contributing to the Harness Developer Hub! Our code owners will review your submission.
Description
PR lifecycle
We aim to merge PRs within one week or less, but delays happen sometimes.
If your PR is open longer than two weeks without any human activity, please tag a code owner in a comment.
PRs must meet these requirements to be merged: