[
https://issues.apache.org/jira/browse/APEXCORE-813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16466285#comment-16466285
]
Chinmay Kolhatkar commented on APEXCORE-813:
--------------------------------------------
[~thw] and others (I wish, there was a way to tag all community):
There are 2 ways to deal with this jira:
1. When we release the apex-core, we also publish binary dist package on
dist.apache.org and then let the docker hub automated build (basically during
apex image building) pick it from dist.apache.org and use it.
2. Irrespective of whether the binary package is present on dist.apache.org,
during docker image build process, we use the given branch (from which
Dockerfile is used) to rebuild the binary package and use it.
First one is clearer but then its not possible to create images on SNAPSHOT
build unless we parameterize the docker build process in some way.
Second way will ensure always building a new binary dist from the branch but
not necessary mean its using the apache released dist package.
Which approach seems better?
> Update docker build steps to use apex bin dist package
> ------------------------------------------------------
>
> Key: APEXCORE-813
> URL: https://issues.apache.org/jira/browse/APEXCORE-813
> Project: Apache Apex Core
> Issue Type: Task
> Reporter: Chinmay Kolhatkar
> Assignee: Chinmay Kolhatkar
> Priority: Major
>
> Currently docker build steps picks up apex deb from bigtop CI for installing
> in apex docker image.
> Because of this docker image generation becomes dependent on update to bigtop
> and then CI build to be generated from that.
> Instead the the binary package of apex can be used in docker image.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
