You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tika.apache.org by "Lewis John McGibbney (Jira)" <ji...@apache.org> on 2024/11/09 22:22:00 UTC
[jira] [Created] (TIKA-4346) Trigger new tika-helm chart release after new tika-docker release
Lewis John McGibbney created TIKA-4346:
------------------------------------------
Summary: Trigger new tika-helm chart release after new tika-docker release
Key: TIKA-4346
URL: https://issues.apache.org/jira/browse/TIKA-4346
Project: Tika
Issue Type: New Feature
Components: tika-helm
Affects Versions: 3.1.0
Reporter: Lewis John McGibbney
Assignee: Lewis John McGibbney
Fix For: 3.1.0
The goal is to automatically trigger a release workflow for [tika-helm|https://github.com/apache/tika-helm] whenever a new [tika-docker|https://hub.docker.com/r/apache/tika] image tag becomes available.
This can be accomplished by [creating a dockerhub webhook|https://docs.docker.com/docker-hub/webhooks/#create-a-webhook] which will post to the relevant (yet to be authored) tika-helm [GitHub Action|https://github.com/apache/tika-helm/tree/main/.github/workflows].
The above workflow will ensure that a downstream tika-helm chart exists for each tika-docker container image and hence encouraging downstream usage/consumption.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)