[
https://issues.apache.org/jira/browse/TINKERPOP-1897?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16381036#comment-16381036
]
ASF GitHub Bot commented on TINKERPOP-1897:
-------------------------------------------
Github user spmallette commented on the issue:
https://github.com/apache/tinkerpop/pull/802
Thanks for doing this @FlorianHockmann - i'm just dumping my brain of
questions and thoughts on this one.
So `mvn deploy` will deploy to where? dockerhub? If so, could you include
something in the dev docs on how you configure your system to allow for that?
i assume we would want it to deploy here:
https://hub.docker.com/u/tinkerpop/ but i can't remember who controls that...i
think it's one of us......
Also, what happens when we do a `mvn deploy` on a SNAPSHOT? that would be
bad right? I think we need to prevent such things from happening somehow.
what does adding this extra step do to the the overall build time (when
building docker is enabled, of course)? I like that you made it a separate
`<profile>` and used the `.docker` pattern we have with `.glv`. Part of this PR
will likely need to include updates for the release process as well.
> Provide Docker images of Gremlin Server and Console
> ---------------------------------------------------
>
> Key: TINKERPOP-1897
> URL: https://issues.apache.org/jira/browse/TINKERPOP-1897
> Project: TinkerPop
> Issue Type: Improvement
> Components: console, server
> Reporter: Florian Hockmann
> Assignee: Florian Hockmann
> Priority: Major
>
> TinkerPop should provide Docker images of Gremlin Server and Gremlin Console
> that are deployed together with each release.
> This originated from the mailing list:
> [https://lists.apache.org/thread.html/744ae19afa9b2fd1984c1e11114dddc588e98786d9c21b633aab8bfa@%3Cdev.tinkerpop.apache.org%3E]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
