[
https://issues.apache.org/jira/browse/OAK-7747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16610578#comment-16610578
]
Francesco Mari commented on OAK-7747:
-------------------------------------
With this issue I didn't want to define a release environment executed in a
batch fashion, but an interactive environment for development purposes. I think
that the {{Dockerfile}} can be repurposed to implement a release job though.
> 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
(v7.6.3#76005)
