STATUS - DRAFT
Introduction
This document details an artifact delivery and systems integration workflow for Tika release artifacts downstream of the canonical Tika Release Process. The table below details all downstream artifacts.
| Name | GitHub URL | Artifact Repository URL | Release Process |
|---|---|---|---|
| tika-docker | https://github.com/apache/tika-docker | https://hub.docker.com/r/apache/tika | Release Process for tika-docker |
| tika-helm | https://github.com/apache/tika-helm | https://artifacthub.io/packages/helm/apache-tika/tika | Release Process for tika-helm |
This ensures that given an official Apache Tika release, artifacts will be generated and released for tika-docker and tika-helm.
The need for a continuous delivery architecture
The Apache Tika project makes several official releases each year. The user community must be able to consume the downstream artifacts (Docker & Helm) shortly after each official Tika release.
As of original writing (May 2024) both tika-docker and tika-helm artifact releases are performed manually on a best case basis. There is no guarantee that artifacts will even be available for a given Tika release. This can be improved for improved consumption of downstream packages artifacts.
An artifact delivery mechanism which integrates the the Tika Java release management process, DockerHub (for tika-docker) and Artifactory (for tika-helm) would provide a convenient, reliable solution for consumers of the downstream Apache Tika artifacts mentioned above. The overwhelming majority of this workflow can be automated via GitHub Actions.
The swminlane diagram below provides the contextual workflow used to deliver downstream Tika artifacts.
Continuous Delivery Workflow