stackabletech / stackabletech/docker-images
chore(java-bases): Update image for 26.11.0
Nobody has claimed this yet.
- Dominant language
- Dockerfile
- Stars
- 22
- Forks
- 6
- Avg merge
- 16h 59m
- Merged PRs (30d)
- 30
Description
Part of https://github.com/stackabletech/docker-images/issues/1641.
Add:x.x.x- Remove:
y.y.y(TBD)
[!TIP]
Please add to the Stackable Engineering project.
[!IMPORTANT]
java-baseuses vector and is used as a base for java products.java-develuses stackable-base and is used to build java products.
Typically product updates will determine which version of Java is required, but
we should also make new versions of Java available for use.
Update tasks
-
Add any new versions of java to bothjava-base/boil-config.tomlandjava-devel/boil-config.toml - Check for and upload new Maven versions (updated directly in the
java-devel/Dockerfile) - Remove versions when there are no long any references (eg:
grep java- **/boil-config.toml | grep "1.8.0")
Related Pull Requests
- Link to the docker-images PR (product update)
Acceptance
[!TIP]
This list should be completed by the assignee(s), once respective PRs have been merged. Once all items have been
checked, the issue can be moved into Development: Done.
- Can build a product image that uses the new version(s)
- Both
java-baseandjava-develhave the same Java versions inboil-config.toml - All kuttl tests pass locally for a product using the new Java version
Testing instructions
# Test a product image can build, eg: ZooKeeper where x.y.z is a valid product
# version using the newly added Java version
boil build zookeeper=x.y.z --strip-architecture --load
kind load docker-image oci.stackable.tech/sdp/zookeeper:x.y.z-stackable0.0.0-dev
# Change directory into one of the operator repositories (eg: zookeeper-operator) and update the
# product version in tests/test-definition.yaml
./scripts/run-tests --test-suite smoke-latest # or similar
Please consider updating this template if these instructions are wrong, or
could be made clearer.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with java-base/boil-config.toml, java-devel/boil-config.toml, and java-devel/Dockerfile to check the Java and Maven versions involved. Build a product image with boil build, load it with kind, then run the relevant operator's ./scripts/run-tests --test-suite smoke-latest. Done means the required versions are synchronized, the product image builds, and the kuttl tests pass.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, java
- Domain
- build-system, devops
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100