My take on this. 1) We can use a profile that will activate if docker is installed 2) If we want to control what get released to the Docker repository under the Apache Jena name then I think we need to have Maven build the docker images. We need to restrict access to the repository so that only "official" builds go there. We need to have jenkins deploy there on successful build. 3) We should establish and document the tags we will add to the docker repository. As a starting point I would say:
latest -- freshest successful build (snapshot or release) release -- the last release. <verson> -- the release for that version. Just my thoughts On Thu, Oct 3, 2019 at 9:52 AM Martynas Jusevičius (Jira) <[email protected]> wrote: > > [ > https://issues.apache.org/jira/browse/JENA-909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16943431#comment-16943431 > ] > > Martynas Jusevičius commented on JENA-909: > ------------------------------------------ > > [~rvesse] I'm not sure I agree, as many projects have been Docker-ized by > completely different maintainers in a different codebase and it all works > just fine. > > But lets assume Maven invokes the Docker build - does that not require > having Docker installed? > > > 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 > > Priority: Major > > Attachments: image-2019-10-02-22-24-12-723.png > > > > > > Provide a Docker launcher and setup documentation for Fuseki2. > > > > -- > This message was sent by Atlassian Jira > (v8.3.4#803005) > -- I like: Like Like - The likeliest place on the web <http://like-like.xenei.com> LinkedIn: http://www.linkedin.com/in/claudewarren
