[ 
https://issues.apache.org/jira/browse/TIKA-4462?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18014219#comment-18014219
 ] 

Lewis John McGibbney commented on TIKA-4462:
--------------------------------------------

Some additional notes. 
 # I updated the [release 
howto|https://cwiki.apache.org/confluence/display/TIKA/Release+Process+for+tika-helm]
 to revert to using the 
[helm-push-artifactory-plugin|https://github.com/belitre/helm-push-artifactory-plugin].
 This is simply a better solution to curl. I plan to fork the archived 
repository and attempt to update it. JFrog seem unwilling to augment their 
JFrog CLI to add helm chart upload functionality. This plugin makes it 
intuitive to generate the Helm package and perform the upload via Helm package 
manager. 
 # I want to automate more of the Helm Chart release process cf. 
https://cwiki.apache.org/confluence/display/TIKA/Release+Process+for+tika-helm#ReleaseProcessfortikahelm-FutureWork

> Release tika-helm 3.2.2
> -----------------------
>
>                 Key: TIKA-4462
>                 URL: https://issues.apache.org/jira/browse/TIKA-4462
>             Project: Tika
>          Issue Type: Task
>            Reporter: Tim Allison
>            Assignee: Lewis John McGibbney
>            Priority: Major
>
> We recently released Tika 3.2.2 and pushed images to docker hub. We should 
> update our helm chart as well.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to