fpiesche commented on PR #19:
URL: https://github.com/apache/tika-docker/pull/19#issuecomment-1793029617
With this most recent set of changes:
* The workflow will automatically trigger if a new version tag (of format
`*.*.*.*`) is created
* The build will run and locally store the image, then
* run the newly-built image
* as per the `docker-tool.sh`, check that the service is responding to
http requests and running as the expected user
* If tests have passed, the image will be pushed to the remote repositories
with the following tags:
* the name of the latest tag
* the Tika version (so e.g. the image tagged `2.8.0` will always be the
latest build out of the `2.8.0.x` tags in the git repository)
* `latest`
And finally, here's an example build [triggered by creating a new GitHub
release](https://github.com/fpiesche/tika-docker/actions/runs/6749676453)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscr...@tika.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
