I like the idea. I use this docker-compose file quite frequently to test nifi and registry integration: https://github.com/kevdoran/flowops/blob/master/docker/demo/nifi-registry/docker-compose.yml
I often replace the nifi or registry image with one built locally (e.g., nifi-dockermaven) depending on what I'm testing and I find it a huge time saver. Centralizing a few of these images and docker-compose files into some aimed at development, testing, or verification would be useful for folks who want to use them, and not required for folks who prefer to build and run things locally without containers. Cheers, Kevin On Thu, Oct 24, 2019 at 12:51 PM Adam Taft <[email protected]> wrote: > > In general I like this idea. I'd like to even suggest a possibly broader > vision that aims towards a more stable build environment that would be the > "reference" environment for building NiFi. > > I have been kicking around and looking at a Docker based build environment > for NiFi. The idea is that you have a well defined build image that can > take any of the NiFi source releases and execute the entire maven > test/build cycle on it. > > I initially thought this would be an easy task, just whip up a new > Dockerfile with the necessary build environment (I based my on Centos, > adding in the java and maven requirements). Surprisingly though, this > turned out to be a difficult task. I experienced all sorts of test errors, > somewhat randomly and seemingly uncorrelated. > > So for now, I have put the idea to the side because I haven't been able to > isolate whether the problems are with the build environment (likely) vs. > the problems being with NiFi source itself. But I would definitely be > interested in contributing and kicking this concept again, if there was > some interest in collaboration. > > Thanks, > Adam > > > On Thu, Oct 24, 2019 at 7:25 AM Mike Thomsen <[email protected]> wrote: > > > Any thoughts on building a few Docker Compose configurations to help people > > test out a new release at vote time? I have a few that could be contributed > > to the repository with a little cleanup. > > > > Mike > >
