nddipiazza opened a new pull request, #2715:
URL: https://github.com/apache/tika/pull/2715

   ## Summary
   
   Moves Docker build infrastructure into the main tika repo so that Docker 
image releases are tied directly to Tika releases, eliminating the need for 
cross-repo coordination with `tika-docker` and `tika-grpc-docker`.
   
   - **Snapshot workflow** (main branch push): builds and pushes `apache/tika`, 
`apache/tika-full`, and `apache/tika-grpc` snapshot images to Docker Hub
   - **Release workflow** (version tag push): builds and pushes versioned + 
`latest` tags for all three images
   - **tika-server Dockerfiles**: copied from `tika-docker` repo (source of 
truth), plus new `Dockerfile.snapshot` variants that use the Maven assembly 
output instead of downloading from Apache mirrors
   - **tika-grpc docker-build**: Dockerfile, entrypoint script, and build 
context assembly script
   - **TikaGrpcServer**: now falls back to a bundled empty 
`default-tika-config.json` from classpath when no `-c` flag is provided, 
matching standard Java application conventions
   - **Tested locally**: all three images (minimal, full, grpc) build and start 
successfully
   
   ## Required Setup
   
   `DOCKERHUB_USERNAME` and `DOCKERHUB_TOKEN` secrets must be configured in the 
repo settings for the workflows to push images.
   
   ## Test plan
   
   - [x] tika-server minimal: HTTP 200 on port 9998, user 35002:35002
   - [x] tika-server full: HTTP 200 on port 9998, user 35002:35002, ImageMagick 
verified
   - [x] tika-grpc: gRPC server starts on port 9090, all plugins loaded, no 
config file required
   - [ ] Test Docker push to personal Docker Hub
   - [ ] Verify snapshot workflow triggers on main merge
   - [ ] Verify release workflow triggers on version tag
   
   🤖 Generated with [Claude Code](https://claude.com/claude-code)


-- 
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: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to