[
https://issues.apache.org/jira/browse/IMPALA-8622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16891480#comment-16891480
]
ASF subversion and git services commented on IMPALA-8622:
---------------------------------------------------------
Commit f689daef7f140fb2e227ee96218f31076b5ba257 in impala's branch
refs/heads/master from Tim Armstrong
[ https://gitbox.apache.org/repos/asf?p=impala.git;h=f689dae ]
IMPALA-8622,IMPALA-8696: fix docker dependencies, add image list
Adds a plain-text space-separated image list in
docker/docker-images.txt. This is generated based on the images built by
CMake, so is kept in sync with images added to or removed from the
CMake file.
Duplicated logic per image is removed - instead there is a helper
function that is called for each daemon image to be built.
Rips out the timestamp mechanism that was intended to avoid unnecessary
container rebuilds, but has turned out to be brittle. Instead the
containers are rebuilt each time the rule is invoked.
This moves some subdirectories so that the image tag matches the
subdirectory, to simplify the build scripts.
Change-Id: I4d8e215e9b07c6491faa4751969a30f0ed373fe3
Reviewed-on: http://gerrit.cloudera.org:8080/13899
Tested-by: Impala Public Jenkins <impala-public-jenk...@cloudera.com>
Reviewed-by: Lars Volker <l...@cloudera.com>
> Generate list of docker images generated by the build
> -----------------------------------------------------
>
> Key: IMPALA-8622
> URL: https://issues.apache.org/jira/browse/IMPALA-8622
> Project: IMPALA
> Issue Type: Sub-task
> Components: Infrastructure
> Reporter: Tim Armstrong
> Assignee: Tim Armstrong
> Priority: Major
> Labels: docker
>
> Some consumers of the Impala docker images will want to publish them to a
> repo. Currently they would have to hardcode a list of the docker images
> produced by the Impala build to publish them, or do something brittle like
> "docker image ls" to deduce what images were built.
> It would be useful if the build produced a list of the images in some
> consumable format that would be updated (either manually or automatically)
> when the set of images changes. If it needs to be manually updated, we should
> have some kind of check to verify that it isn't stale.
> One option is to produce JSON, something like:
> {noformat}
> {
> “docker_images”: {
> “impala_base”: “$docker_registry/impala_base”,
> ” impalad_coord_exec”: “$docker_registry/impalad_coord_exec”,
> ....
> }
> }
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org
For additional commands, e-mail: issues-all-h...@impala.apache.org
