[
https://issues.apache.org/jira/browse/CASSANDRA-17429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17731501#comment-17731501
]
Michael Semb Wever commented on CASSANDRA-17429:
------------------------------------------------
bq. I was told it was intentional to use image with dependencies for one JDK
and without dependencies for another.
Not sure what this is a reference to. But CASSANDRA-18133 will be moving
images in-tree, allowing such differences between branches (because different
branches depend on different system dependencies: jdk, python, jna, etc). This
will remove the notion of "latest", and images will simply be based on the
md5sum of the docker image. It is planned that there will be a post-commit CI
deployment of the docker image, so (unmodified) images for each branch can be
pulled. (Build scripts will automatically first pull, and if not found will
then build, the image.)
> Use only one image for all CircleCI builds; Switch to "latest" tag
> ------------------------------------------------------------------
>
> Key: CASSANDRA-17429
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17429
> Project: Cassandra
> Issue Type: Task
> Components: CI
> Reporter: Ekaterina Dimitrova
> Assignee: Ekaterina Dimitrova
> Priority: Normal
>
> While working on the latest CircleCI issues, we noticed some inconsistencies
> in our config.
> There were different images used in CircleCI for Java 8 and Java 11.
> We need to use only the latest images everywhere, same as in Jenkins.
> Also, we use specific date tag which is inconvenient as every time a new
> image is published, we need to change the tag in config.yml on all Cassandra
> branches. Better to switch to "latest" tag as we already use it successfully
> in Jenkins.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
