This commit modifies the Git workflow for building the Helm chart
for Paperless NGX. The primary change is the update of the
triggering branch from 'patch-new-paperless' to 'main' for push
events. Additionally, the paths filter is re-enabled to ensure
that the workflow only triggers when changes are made to
"charts/paperless-ngx/Chart.yaml".
These adjustments were necessary to align the workflow with the
project's main branch, ensuring that any updates to the Helm
chart are promptly built and packaged. There are no breaking
changes in this update, but the workflow will not execute for
changes on other branches.
The workflow file for building the Paperless-NGX Helm chart
has been updated. The path specification for the "push" event
has been commented out, allowing the workflow to trigger for
any changes to the branch rather than just modifications to
the "Chart.yaml" file.
Additionally, the Helm repository URL for "bjw-s" has been
corrected to point to the proper location at
"bjw-s-labs.github.io/helm-charts/" to ensure that the latest
charts are accessible.
These changes help improve the workflow flexibility and
correct repository access.
Updated the APP environment variable in the Helm package job from
'charts/pperless-ngx' to 'charts/paperless-ngx'. This change was
necessary to correct the path to the Paperless NGX chart, ensuring
that the workflow refers to the correct directory. The previous path
contained a typo which would have resulted in build errors. There are
no breaking changes introduced with this update.
This commit introduces a new GitHub Actions workflow defined in
`.gitea/workflows/build-chart-paperless-ngx.yml` to automate the
building and packaging of the Helm chart for the
Paperless-ng project. The workflow triggers on pushes to the
`main` branch when changes are made to the `charts/paperless-ngx/Chart.yaml`
file.
The key steps in this workflow include checking out the repository,
extracting the Helm chart's application name and version from the
`Chart.yaml`, setting up Helm, updating dependencies, linting the
chart, and finally packaging it.
The resulting Helm package is then uploaded to a specified Helm
registry using the credentials stored in the repository's secrets.
This automation is important for ensuring that the Helm chart
can be consistently and reliably built with each update, enhancing
the deployment process.
