Plugin Step Settings
This topic provides settings for the CI Plugin step.
Plugins are Docker containers that perform predefined tasks and are configured as steps in your stage. Plugins can be used to deploy code, publish artifacts, send notifications, and more.
In this topic:
- Container Registry
- Image Pull Policy
- Run as User
- Set container resources
- See Also
The unique name for this step.
See Tags Reference.
Harness Connector for the container registry where the plugin image is located.
The name of the Plugin Docker image.
The image name should include the tag and will default to the latest tag if unspecified.
You can use any Docker image from any Docker registry, including Docker images from private registries.
Enable this option to run the container with escalated privileges. This is the equivalent of running a container with the Docker
Plugin-specific settings. Please refer to plugin documentation.
See Drone plugins docs.
Image Pull Policy
Select an option to set the pull policy for the image.
- Always: the kubelet queries the container image registry to resolve the name to an image digest every time the kubelet launches a container. If the kubelet encounters an exact digest cached locally, it uses its cached image; otherwise, the kubelet downloads (pulls) the image with the resolved digest, and uses that image to launch the container.
- If Not Present: the image is pulled only if it is not already present locally.
- Never: the image is assumed to exist locally. No attempt is made to pull the image.
Run as User
Set the value to specify the user id for all processes in the pod, running in containers. See Set the security context for a pod.
Set container resources
Maximum resources limit values for the resources used by the container at runtime.
Maximum memory that the container can use.
You can express memory as a plain integer or as a fixed-point number using one of these suffixes: G, M.
You can also use the power-of-two equivalents: Gi, Mi.
Limit the number of cores that the container can use.
Limits for CPU resources are measured in cpu units.
Fractional requests are allowed. The expression 0.1 is equivalent to the expression 100m, that can be read as one hundred millicpu.
Timeout for the step. Once the timeout is reached, the step fails, and the Pipeline execution continues.