[
https://issues.apache.org/jira/browse/JENA-909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14392630#comment-14392630
]
Stian Soiland-Reyes edited comment on JENA-909 at 4/2/15 12:14 PM:
-------------------------------------------------------------------
(See my comments on JENA-868 there)
While fixing JENA-868 would be nice for the docker image, it is not essential
as you can override with --port=8080, which I included in the README.
My biggest question is how it would fit into the release process; I propose:
jena-fuseki2/jena-fuseki-docker is part of the Maven build and release (so that
its version number gets bumped) - but it doesn't actually produce the docker
image. (Otherwise we would require Release Manager to have Docker installed.)
The docker image does "mvn install" on this module inside the container to pick
up the distribution.
Then we make an organization https://registry.hub.docker.com/u/apache-jena/ and
set up jena-fuseki as an automatic build from http://github.com/apache/jena/
(INFRA will need to approve the connection once) - we won't have builds from
master, but just from fixed tags which you can just edit in the docker hub UI.
This will be more official than "stain/jena-fuseki".
So then if there's a new release, anyone given membership to
https://registry.hub.docker.com/u/apache-jena/ (presumably PMC or committers)
can do is simply to edit the list of tags for jena-fuseki and add the new
github tag as the new LATEST - registry.hub.docker.com will build it - which
means simply it will download and unpack the fuseki 2 distribution using Maven.
was (Author: soilandreyes):
(See my comments on JENA-868 there)
While fixing JENA-868 would be nice for the docker image, it is not essential
as you can override with --port=8080, which I included in the README.
My biggest question is how it would fit into the release process; I propose:
jena-fuseki2/jena-fuseki-docker is part of the Maven build and release (so that
its version number gets bumped) - but it doesn't actually produce the docker
image. (Otherwise we would require Release Manager to have Docker installed.)
The docker image does "mvn install" on this module inside the container to pick
up the distribution.
Then we make an organization https://registry.hub.docker.com/u/jena/ and set up
jena-fuseki as an automatic build from http://github.com/apache/jena/ (INFRA
will need to approve the connection once) - we won't have builds from master,
but just from fixed tags which you can just edit in the docker hub UI. This
will be more official than "stain/jena-fuseki".
So then if there's a new release, anyone given membership to
https://registry.hub.docker.com/u/jena/ (presumably PMC or committers) can do
is simply to edit the list of tags for jena-fuseki and add the new github tag
as the new LATEST - registry.hub.docker.com will build it - which means simply
it will download and unpack the fuseki 2 distribution using Maven.
> Create Docker launcher for Fuseki
> ---------------------------------
>
> Key: JENA-909
> URL: https://issues.apache.org/jira/browse/JENA-909
> Project: Apache Jena
> Issue Type: Improvement
> Components: Fuseki
> Reporter: Andy Seaborne
>
> Provide a Docker launcher and setup documentation for Fuseki2.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
