[
https://issues.apache.org/jira/browse/HBASE-24466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17597257#comment-17597257
]
Sean Busbey commented on HBASE-24466:
-------------------------------------
picking this back up again. for folks not familiar with docker and container
stuff a bit of background. A "named volume" is a way to consistently refer to a
storage location that's available to one or more containers but not the host
OS. in k8s terminology they're like a ReadWriteMany PVC but only for the
containers on the one host handling the docker daemon.
The idea here would be that for a given release line (e.g. 2.5.0) you would
reuse the named volume across release candidates to store all the third party
artifacts since those usually don't change between candidates. Maybe we could
reuse it across patch releases in the same minor release line. Importantly we
would need to make sure we aren't reusing any of the artifacts we create in the
build.
This is close to what happens if you use the release scripts without the docker
container and set REPO to point at your local maven repository.
> Release scripts in docker mode should be able to use a named volume for maven
> repo
> ----------------------------------------------------------------------------------
>
> Key: HBASE-24466
> URL: https://issues.apache.org/jira/browse/HBASE-24466
> Project: HBase
> Issue Type: Improvement
> Components: build, community
> Reporter: Sean Busbey
> Assignee: Sean Busbey
> Priority: Major
>
> Allow optional volume name to use to mount the maven repo so we get reuse of
> third party artifacts between runs.
> Forcefully remove artifacts we build from it (assuming we can't make a
> read-only one that's shared for third party dependencies and an isolated one
> that's for what we're building)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
