Package: chartpress
chartpressChartpress automate basic Helm chart development work. It is tightly used in development of theJupyterHubandBinderHubHelm charts.FeaturesChartpress can do the following with the help of some configuration.Update Chart.yaml's version appropriatelyBuild docker images and tag them appropriatelyPush built images to a docker image repositoryUpdate values.yaml to reference the built imagesPublish a chart to a Helm chart registry based on GitHub pagesReset changes to Chart.yaml and values.yamlHow chart version and image tags are determinedChartpress will infer chart versions and image tags using a few key pieces of
information.tag: If not directly set by--tag, it will be inferred from most recent
commit that is tagged in thecurrent branch(as determined bygit describe)
or be set to 0.0.1 if no commit is tagged.If thetaghas a leadingvbut is otherwise a validSemVer2version, thevwill be stripped from Chart.yaml
before its set as Helm 3 requires Helm chart versions to be SemVer2
compliant.The latest commit modifying content in arelevant pathsincetag.n: The number of commits since the latest tagged commit on the branch, as an integer.hash: The latest commit's abbreviated hash, which is often 7-8 characters,
prefixed withh.Iftag(like0.10.0or0.10.0-beta.1) contains a-, atag.git.n.hashformat will be used, and otherwise atag-0.dev.git.n.hashformat will be used.If--longis specified or not. If--longis specified, tagged commits
will always be written out with the.git.n.hashpart appended to it, looking something
like1.0.0-0.dev.git.0.habcd123When producing a development version (with.git.n.hashon the end),
Thebaseversion can come from one of two places,
depending on your configuration.
SeeControlling development versionfor more info.Examples chart versions and image tagsThis is a list of realistic chart versions and/or image tags in a chronological
order that could come from using chartpress.0.8.0
0.8.0-0.dev.git.4.hasdf123
0.8.0-0.dev.git.10.hsdfg234
0.9.0-beta.1
0.9.0-beta.1.git.12.hdfgh345
0.9.0-beta.1.git.15.hfghj456
0.9.0-beta.2
0.9.0-beta.2.git.20.hghjk567
0.9.0-beta.3
0.9.0RequirementsThe following binaries must be in yourPATH:gitdockerhelmIf you are publishing a chart to GitHub Pages create agh-pagesbranch in the
destination repository.Installationpip install chartpressUsageIn a directory containing achartpress.yaml, run:chartpressto build your chart(s) and image(s). Add--pushto publish images to docker
hub and--publish-chartto publish the chart and index to gh-pages.usage: chartpress [-h] [--push] [--force-push] [--publish-chart]
                  [--force-publish-chart] [--extra-message EXTRA_MESSAGE]
                  [--tag TAG | --long] [--image-prefix IMAGE_PREFIX] [--reset]
                  [--no-build | --force-build]
                  [--builder {docker-build,docker-buildx}]
                  [--platform PLATFORM] [--list-images] [--version]

Automate building and publishing helm charts and associated images. This is
used as part of the JupyterHub and Binder projects.

optional arguments:
  -h, --help            show this help message and exit
  --push                Push built images to their image registries, but not
                        if it would replace an existing image.
  --force-push          Push built images to their image registries,
                        regardless if it would replace an existing image.
  --publish-chart       Package a Helm chart and publish it to a Helm chart
                        registry constructed with a GitHub git repository and
                        GitHub pages, but not if it would replace an existing
                        chart version.
  --force-publish-chart
                        Package a Helm chart and publish it to a Helm chart
                        registry constructed with a GitHub git repository and
                        GitHub pages, regardless if it would replace an
                        existing chart version
  --extra-message EXTRA_MESSAGE
                        Extra message to add to the commit message when
                        publishing charts.
  --tag TAG             Explicitly set the image tags and chart version.
  --long                Use this to always get a build suffix for the
                        generated tag and chart version, even when the
                        specific commit has a tag.
  --image-prefix IMAGE_PREFIX
                        Override the configured image prefix with this value.
  --reset               Skip image build step and reset Chart.yaml's version
                        field and values.yaml's image tags. What it resets to
                        can be configured in chartpress.yaml with the resetTag
                        and resetVersion configurations.
  --no-build, --skip-build
                        Skip the image build step.
  --force-build         Enforce the image build step, regardless of if the
                        image already is available either locally or remotely.
  --builder {docker-build,docker-buildx}
                        Container build engine to use, docker-build is the
                        standard Docker build command.
  --platform PLATFORM   Build the image for this platform, e.g. linux/amd64 or
                        linux/arm64. This argument can be used multiple times
                        to build multiple platforms under the same tag. Only
                        supported for docker buildx. If --push is set or if
                        multiple platforms are passed the image will not be
                        loaded into the local docker engine.
  --list-images         print list of images to stdout. Images will not be
                        built.
  --version             show program's version number and exitConfigurationAchartpress.yamlfile contains a specification of charts and images to build
for each chart. Below is an examplechartpress.yamlfile.charts:# list of charts by name# each name should be the name of a Helm chart-name:binderhub# Directory containing the chart, relative to chartpress.yaml.# Can be omitted if the directory is the same as the chart name.chartPath:helm-charts/binderhub# the prefix to use for built imagesimagePrefix:jupyterhub/k8s-# tag to use when resetting the chart values# with the --reset flag. It defaults to "set-by-chartpress".resetTag:latest# version to use when resetting the Chart.yaml's version field with the# --reset flag. It defaults to "0.0.1-set.by.chartpress". This is a valid# SemVer 2 version, which is required for a helm lint command to succeed.resetVersion:1.2.3-dev# baseVersion sets the base version for development tags,# instead of using the latest tag from `git describe`.# This gives you more control over development version tags# and lets you ensure prerelease tags are always sorted in the right order.# Only useful when publishing development releases.# Recommended together with a version-bumping tool like `tbump`.# if baseVersion is not a prerelease version (no -suffix),# the suffix `-0.dev` will be appended.## Alternatively baseVersion can be set to "major", "minor", or "patch", then# baseVersion will be calculated based on the latest version tag from `git# describe`, but have its "major", "minor", or "patch" version increment if# the version isn't a pre-release.baseVersion:3.2.1-0.dev# The git repo whose gh-pages contains the charts. This can be a local# path such as "." as well but if matching <organization>/<repo> will be# assumed to be a separate GitHub repository.repo:git:jupyterhub/helm-chartpublished:https://jupyterhub.github.io/helm-chart# Additional paths that when modified should lead to an updated Chart.yaml# version, other than the chart directory in <chart name> or any path that# influence the images of the chart. These paths should be set relative to# chartpress.yaml's directory.paths:-../setup.py-../binderhub# images to build for this chart (optional)images:binderhub:# imageName overrides the default name of the image. The default name# is the imagePrefix augmented with the key of this configuration. It# would be jupyterhub/k8s-binderhub in this case.imageName:jupyterhub/k8s-custom-image-name# Build arguments to be passed using docker's --build-arg flag as# --build-arg <key>=<value>. TAG and LAST_COMMIT are expandable.buildArgs:MY_STATIC_BUILD_ARG:"helloworld"MY_DYNAMIC_BUILD_ARG:"{TAG}-{LAST_COMMIT}"# Build options to be passed to the docker build command. Pass a list# of strings to be appended to the end of the build command. These are# passed directly to the command line, so prepend each option with "--"# like in the examples below. TAG and LAST_COMMIT are expandable.extraBuildCommandOptions:---label=maintainer=octocat---label=ref={TAG}-{LAST_COMMIT}---rm# contextPath is the path to the directory that is to be considered the# current working directory during the build process of the Dockerfile.# This is by default the folder of the Dockerfile. This path should be# set relative to chartpress.yaml.contextPath:..# By default, changes to the contextPath will make chartpress rebuild# the image, but this option make that configurable.rebuildOnContextPathChanges:false# Path to the Dockerfile, relative to chartpress.yaml. Defaults to# "images/<image name>/Dockerfile".dockerfilePath:images/binderhub/Dockerfile# Path(s) in <chart name>/values.yaml to be updated with image name and# tag.valuesPath:-singleuser.image-singleuser.profileList.0.kubespawner_override.image# Additional paths, relative to chartpress.yaml's directory, that should# be used to indicate that a new tag of the image is required, aside# from the contextPath and dockerfilePath for building the image itself.paths:-assets# If chartpress is used to build images for multiple architectures but# not all of those architectures are supported by an image they can be# skippedskipPlatforms:-linux/arm64Controlling development versionsLike some "package version in version control" tools,
you don't need to manage versions at all in chartpress except by tagging commits.However, relying only on tags results in "development versions" (versions published from commits after a release)
having somewhat confusing prerelease versions.After publishing e.g.1.2.3, the next version will be1.2.3-0.dev.git.10.habc.
According to Semantic Versioning,
this is a "pre release" (good, it should be excluded from default installation),
but it means it comesbefore1.2.3 (wrong! it's 1 commitnewerthan 1.2.3).
This is because prereleases should be defined relative to thenextrelease,
not thelastrelease. But git tags only store thelastrelease!Chartpress 2.0 adds an optionchart.baseVersion,
which allows setting the base version of development tags explicitly,
instead of using the version of the last tag found viagit describe.The main benefits of this are:ensuring that published prerelease versions show up in the right order, andgiving you control over the version of a prerelease chart (is it 2.0.0-0.dev or 1.3.1-0.dev?)Instead of publishing the sequence:1.2.31.2.3-0.dev.git.10.habc (later than 1.2.3, but sortsbefore1.2.3!)You can publish1.2.31.3.0-0.dev.git.10.habc (prerelease based on thenextversion, notlast)where chartpress will use the version in yourbaseVersionconfig as the base version,
instead of the last tag on the branch.This takes some extra configuration, and steps in your release process:You must setbaseVersion: 1.2.3-0.devin your chartpress.yaml to yournextprerelease:charts:-name:mychartbaseVersion:1.2.3-0.devYou must update baseVersion, especially after making a release.
We recommend using a version bumping tool liketbumpto keep your baseVersion config and git tags in sync.A release process would generally look like this:V=1.2.3# tbump updates version, commits changes, tags commit, pushes branch and tagtbump"$V"# back to developmentNEXT_V=1.2.4-0.dev# bump version config, but no tag for starting developmenttbump--no-tag"${NEXT_V}"Any prerelease fields (such as-0.devabove, or-alpha.1)
will be left as-is, with the.git.n.hashsuffix added.
If there is no prerelease (e.g. on the exact commit of a tagged release),-0.devwill be added to the base version.
Youmustupdate baseVersion after making a release,
orchartpress --resetwill fail due to incorrect ordering of versions.A sample tbump config file can be found inour tests.CaveatsShallow clonesChartpress detects the latest commit that changed a directory or file when
determining the version and tag to use for charts and images. This means that
shallow clones should not be used because if the last commit that changed a
relevant file is outside the shallow commit range, the wrong chart version and
image tag will be assigned.Avoiding shallow clones with GitHub ActionsGitHub Workflow's commonly used GitHub Action called actions/checkout have a
clone clone-depth of 1 by default, configure it to make a full clone instead.steps:-uses:actions/checkout@v2with:# chartpress need the git branch's tags and commitsfetch-depth:0Command cachingChartpress caches the results of some commands to improve performance.
This means chartpress should not be used as an importable library.DevelopmentTesting of this python package can be done usingpytest. For more details on the
testing, seetests/README.md.# install chartpress locallypipinstall-e.# install dev dependenciespipinstall-rdev-requirements.txt# format and lint codepre-commitrun-a# run testspytest--verbose--exitfirst# some tests push to a local registry, you can skip thesepytest--verbose--exitfirst-m'not registry'