DUE TO SPAM, SIGN-UP IS DISABLED. Goto Selfserve wiki signup and request an account.
| Table of Contents |
|---|
| Status | ||||||
|---|---|---|---|---|---|---|
|
Introduction
This document details a Continuous Delivery 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 expect that they will 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 lag damages the Tika project brand and raises questions about support for these official downstream packages artifacts.
An artifact delivery A Continuous Delivery mechanism which integrates the Apache Release mirrors, 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 systems Integration swminlane diagrams diagram below provide provides the contextual workflow used to deliver downstream Tika artifacts.