jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Davide Giannella (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (OAK-7747) Use Docker to define the development environment
Date Tue, 11 Sep 2018 13:18:00 GMT

    [ https://issues.apache.org/jira/browse/OAK-7747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16610561#comment-16610561

Davide Giannella commented on OAK-7747:

I like the idea. However my private experiments about Docker+Oak resulted in oak testing always
timing out and failing the build. Maybe worth some investigations. Maybe not.

> Use Docker to define the development environment
> ------------------------------------------------
>                 Key: OAK-7747
>                 URL: https://issues.apache.org/jira/browse/OAK-7747
>             Project: Jackrabbit Oak
>          Issue Type: Wish
>            Reporter: Francesco Mari
>            Assignee: Francesco Mari
>            Priority: Major
>         Attachments: OAK-7747-01.patch
> In order to improve the reproducibility of our development (and release?) builds and
to facilitate the collaboration with external contributors, I propose to define a recommended
development environment in a Docker container. The container should provide the most commonly
used tools (Java, Maven, Subversion, Git) and should integrate with the local environment
of the developer, where the configuration files for all that software lives.
> The attached patch is an attempt to implement this idea. The {{Makefile}} builds a Docker
image, starts a container from that image and starts a shell inside the container. The {{Makefile}}
also mounts enough volumes to make the local configuration of Git, Subversion and SSH available
to the software in the container. 
> A user only needs to type {{make}} from the root of the source tree to start a shell.
Any command in the shell, e.g. {{mvn clean install}}, will work on the actual source tree
from the local machine, since that is also mounted as a volume. This enables the user to work
with his favourite IDE on his local machine and build the code using the container, seamlessly.

This message was sent by Atlassian JIRA

View raw message