On Mon, Sep 19, 2016 at 10:26 PM, Robert Munteanu <romb...@apache.org> wrote:
> ...Another benefit is that if a contributor wants to reproduce a problem
> on Jenkins, all the effort that is required is to run Jenkins via
> docker, install a couple of plugins, create the seed job and all the
> Jenkins configuration is replicated...
This sounds great, with the job creation code in svn as you suggest.
Bonus points for having a Docker file in svn so that we can easily
compare a local Jenkins build with the https://builds.apache.org/ one.