key/value
pairs), which can be referenced by downstream stages.prerequisite check
can be used to ensure that a stage will be executed only when specific conditions are met.Field | Required? | Description |
Application | Yes | Lists all the applications that you have access to |
Deployment Pipeline | Yes | Lists all the deployment pipelines under the application |
Wait for execution result | No | If you select to wait, the final execution status of the sub-pipelines is deemed as the status of this stage. Otherwise, when the execution of the sub-pipelines starts, the status of this stage will be flagged as "successful". |
header
and the payload in JSON format. By default, if calling a webhook returns 2XX
or 3XX
, the stage execution has succeeded; if it returns 4XX
or 5XX
, the execution has failed. The final status of the webhook's URL and payload will be displayed in the pipeline execution details.Webhook
object of the stage context, so that the payload can be referenced in the subsequent pipeline expressions. For example, you can use the following expression to obtain the final status of the webhook execution:${#stage("My Webhook Stage")["context"]["webhook"]["statusCode"]}
Field | Required? | Description |
Cloud Service | Yes | Cloud service type. Kubernetes and Tencent Cloud are supported. |
Cloud Account | Yes | Cloud account that manages resource objects |
Namespaces | Yes | Namespaces where the service groups belong |
Clusters | Yes | Clusters where the service groups belong |
Disable Options | Yes | Specifies the rules for disabling options |
Field | Required? | Description |
Cloud Service | Yes | Cloud service type. Kubernetes and Tencent Cloud are supported. |
Cloud Account | Yes | Cloud account that manages resource objects |
Namespaces | Yes | Namespaces where the service groups belong |
Clusters | Yes | Clusters where the service groups belong |
Disable Options | Yes | Specifies the rules for disabling options |
Health Check | Yes | Only refers to the health check that Tencent Cloud provides when you perform this task |
Field | Required? | Description |
Cloud Service | Yes | Cloud service type. Kubernetes and Tencent Cloud are supported. |
Cloud Account | Yes | Cloud account that manages resource objects |
Namespaces | Yes | Namespaces where the service groups belong |
Clusters | Yes | Clusters where the service groups belong |
Scale-Down Options | Yes | Specifies scale-down options |
Field | Required? | Description |
Cloud Service | Yes | Cloud service type. Kubernetes and Tencent Cloud are supported. |
Cloud Account | Yes | Cloud account that manages resource objects |
Regions | Yes | Regions where the service groups belong |
Clusters | Yes | Clusters where the service groups belong |
Health Check | Yes | Only refers to the health check that Tencent Cloud provides when you perform this task |
Field | Required? | Description |
Cloud Service | Yes | Cloud service type. Kubernetes and Tencent Cloud are supported. |
Cloud Account | Yes | Cloud account that manages resource objects |
Namespaces | Yes | Namespaces where the service groups belong |
Clusters | Yes | Clusters where the service groups belong |
Target Service Groups | Yes | Specifies matching rules for service groups |
Field | Required? | Description |
Cloud Service | Yes | Cloud service type. Kubernetes and Tencent Cloud are supported. |
Cloud Account | Yes | Cloud account that manages resource objects |
Regions | Yes | Regions where the service groups belong |
Clusters | Yes | Clusters where the service groups belong |
Target Service Groups | Yes | Specifies matching rules for service groups |
Health Check | Yes | Only refers to the health check that Tencent Cloud provides when you perform this task |
Field | Required? | Description |
Cloud Service | Yes | Cloud service type. Kubernetes and Tencent Cloud are supported. |
Cloud Account | Yes | Cloud account that manages resource objects |
Namespaces | Yes | Namespaces where the service groups belong |
Clusters | Yes | Clusters where the service groups belong |
Target Service Groups | Yes | Specifies matching rules for service groups |
Field | Required? | Description |
Cloud Service | Yes | Cloud service type. Kubernetes and Tencent Cloud are supported. |
Cloud Account | Yes | Cloud account that manages resource objects |
Regions | Yes | Regions where the service groups belong |
Clusters | Yes | Clusters where the service groups belong |
Target Service Groups | Yes | Specifies matching rules for service groups |
Rebake
in the stage configuration. For more information, see Packer by HashiCorp.Field | Required? | Description |
Cloud Account | Yes | Tencent Cloud Account |
Regions | Yes | Regions where the clusters belong |
Clusters | Yes | Specifies the clusters to be rolled back |
Health Check | Yes | Only refers to the health check that Tencent Cloud provides when you perform this task |
Docker image
)Deploy (Manifest)
stage in advance.Deploy (Manifest)
stage.Text
type, you can directly edit the YAML file content in the text field.{"name": "Deploy my manifest", // human-readable name"type": "deployManifest", // tells orchestration engine what to run"account": "nudge", // account (k8s cluster) to deploy to"cloudProvider": "kubernetes","source": "text","manifest": {// manifest contents go here}}
Deploy (Manifest)
stage must be the text files that contain the manifest definition, which may exist in GitHub repositories or GCS. For more information, see Deployment Pipeline Settings.expected artifacts
at the upstream stages, you can reference them at the Deploy (Manifest)
stage:Artifact
for the Manifest Source field, you can deploy the artifacts offered by upstream stages. Make sure that your cloud account has permission to download artifacts..*\\yml
to use all yml
files as artifacts, then all matching yml
files will be deployed when the Deploy (Manifest)
stage is executed.flag
in the Docker image or ConfigMap. Therefore, CODING-CD provides excellent adaptability to these resource type changes.gcr.io/my-project/my-image
, whose digest value is sha256:c81e41ef5e...
. In the pipeline, you configure a deployment stage with the following manifest content:# ... rest of manifestcontainers:- name: my-containerimage: gcr.io/my-project/my-image# rest of manifest ...
changes in the content of the Docker image
, the pipeline orchestration engine will distribute the Docker image artifact along with the manifest at the deployment stage to the Clouddriver
component for processing. The content of the manifest that is eventually deployed will be as follows:# ... rest of manifestcontainers:- name: my-containerimage: gcr.io/my-project/my-image@:sha256:c81e41ef5e...# rest of manifest ...
gcr.io/my-project/my-image
must be bound to the manifest. Otherwise, the stage execution will fail:Statically Specify Target
for Selector
Field | Required? | Description |
Cloud Account | Yes | Cloud account that manages resource objects |
Namespace | Yes | Namespace where the resource objects belong |
Selector | Yes | Statically specifies the target resources to be deleted by name |
Kind | Yes | Resource object type |
Name | Yes | Resource object name (such as ReplicaSet resources nginx-deployment-5dfd77bbf9) |
Dynamically Select Target
for Selector
Field | Required? | Description |
Cloud Account | Yes | Cloud account that manages resource objects |
Namespace | Yes | Namespace where the resource objects belong |
Selector | Yes | Statically specifies the target resources to be deleted by name |
Kind | Yes | Resource object type |
Clusters | Yes | Resource object name (such as ReplicaSet resources nginx-deployment-5dfd77bbf9) |
Target | Yes | Selects matching rules for resource objects |
Statically Specify Target
for Selector
Field | Required? | Description |
Cloud Account | Yes | Cloud account that manages resource objects |
Namespace | Yes | Namespace where the resource objects belong |
Selector | Yes | Statically specifies the target resources to be deleted by name |
Kind | Yes | Resource object type |
Name | Yes | Resource object name (such as ReplicaSet resources nginx-deployment-5dfd77bbf9) |
Dynamically Select Target
for Selector
Field | Required? | Description |
Cloud Account | Yes | Cloud account that manages resource objects |
Namespace | Yes | Namespace where the resource objects belong |
Selector | Yes | Dynamically selects resource objects by cluster and target field |
Kind | Yes | Resource object type |
Cluster | Yes | Cluster where the resource objects belong |
Target | Yes | Selects matching rules for resource objects |
Match Target by Tag
for Selector
Field | Required? | Description |
Cloud Account | Yes | Cloud account that manages resource objects |
Namespace | Yes | Namespace where the resource objects belong |
Selector | Yes | Matches resource objects according to the specified tag rules |
Kind | Yes | Resource object type |
Labels | Yes | Matches all the resource objects of the specified types if no rules are set |
Field | Required? | Description |
Delete Cascade | No | If this field is checked, all the resource objects managed by this resource object (for example, all the pods managed by a ReplicaSet) will be deleted. If this field is not checked, orphan resources may be generated. |
Grace Period | No | (Optional) Specifies a termination time for the resource object, which will overwrite the time set in the manifest. |
Was this page helpful?