[ 
https://issues.apache.org/jira/browse/GEODE-60?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14746212#comment-14746212
 ] 

jun aoki commented on GEODE-60:
-------------------------------

hi [~markito], thank you for writing up!
Many of them make sense to me except a couple, but let me try to use your image 
instead of making another one. 

* About the centos version.
How about using a specific centos version (centos7 is fine with me) but not 
"latest" as we do not have a control of what is really latest of centos. 
* regarding dockerhub,
It should be the way to go of course but let's keep the Dockerfile in the repo 
(which you do already) so that just in case dockerhub is down, it would not 
block us from doing our business

Also maybe a good idea in your dockerfile to have Apache license signature and 
maintainer to be geode dev mailing list address. Let me take care of it too if 
your Dockerfile works for this ticket.

> Geode build environment within Docker to enable anybody and on any OS and any 
> environment can build Geode as long as there is Docker
> ------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: GEODE-60
>                 URL: https://issues.apache.org/jira/browse/GEODE-60
>             Project: Geode
>          Issue Type: Sub-task
>          Components: build
>            Reporter: jun aoki
>            Assignee: jun aoki
>         Attachments: GEODE-60-2.patch, GEODE-60-3.patch, GEODE-60-4.patch, 
> GEODE-60.patch
>
>
> geode build is on gradle and seems very tidy but it still requires third 
> party libraries, like Java.
> Let's have a Docker environment so that at least we have an reliable 
> immutable environment and we can use it on CI on builds.apache.org 
> https://builds.apache.org/view/E-G/view/Geode/
> (From my experience, It is a bit of pain to find a right environment on 
> builds.a.o but Docker is a cure so far.) 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to