cloudbees-io/Helm chart install

Using helm to install a chart

View on GitHub

Trust Signals

Scorecard Score
not yet scored
Maintenance Recency
Activelast commit Jul 7, 2026
License
MIT

Pinned Snippet

workflow.ymlSHA-pinned
uses: cloudbees-io/helm-install@462b316f6788f32f1c5d90ed21ee6da690649d56 # v1.1.27

tags can be moved; commit SHAs can't. why a SHA?

namedescriptionrequireddefault
release-nameHelm release nameyes
namespaceKubernetes namespace to install the chart in, created if missingdefault
create-namespaceWhether to create the namespace if it does not existtrue
versionVersion of the chart to be installed
values-filePath to a values file relative to the workspace
values-filesList of values files relative to the workspace separated by newline
valuesAn inline YAML representation of a values file passed to the Helm command
timeoutHelm chart installation timeout. However, `Deployment.spec.progressDeadlineSeconds` takes precedence if it is defined with a lower value within the chart's manifests. 10m
chart-locationHelm chart location, can be a URL, a local chart archive, chart repo alias/chart name or an unpacked chart directory yes
max-historyMaxHistory limits the maximum number of revisions saved per release10
debugExecute the helm command in debug modefalse
dependency-buildBuild dependencies based on the contents of Chart.lock filefalse
env-vars-fileAn optional file with key value pairs of the format 'export key=value' to export in the environment before execution of the helm commands.
waitenables waiting for deployments to stabilizetrue
dry-runSimulate an upgrade, without actually doing itfalse
registry-configurationCloudBees registry configuration file containing the registries to use for loading images. By default it uses the file containing the registries configured under 'Integrations' in the CloudBees platform. ${{ cloudbees.registries }}
namedescription
release-revisionThe helm release revision number after install/upgrade