Yes, it certainly can be done, but I think there is a lot of work to get there, as our test machines would need to be docker containers to fit in to that environment versus AWS VMs/images + puppet.
Also, we currently do a heavy amount of resource usage for the level of testing we run for every pull request and nightly testing. It would be heavy burden on ASF infrastructure compared to other projects, perhaps too heavy. Our current build/test automation is in a public github repo. While Esgyn is paying the bill for the AWS resources, it is open to the community to see how things are working. None of it is running internal to Esgyn network (even though domain name might look that way). It is also open to anyone in community willing to help maintain current services and/or migrate it to ASF. --Steve > -----Original Message----- > From: Pierre Smits [mailto:[email protected]] > Sent: Sunday, March 5, 2017 10:32 AM > To: [email protected] > Subject: Re: Jenkins testing change > > I believe it would be in the best interest of the project if the build/test > environment used (Jenkins) would be migrated to the ASF infrastructure. > While I appreciate the help provided by Esgyn (many thanks for that), it is > a less desirable and the ASF has ample means available to replicate the > setup required. > > WDYT? > > Best regards, > > Pierre Smits > > ORRTIZ.COM <http://www.orrtiz.com> > OFBiz based solutions & services > > OFBiz Extensions Marketplace > http://oem.ofbizci.net/oci-2/ > > On Sun, Mar 5, 2017 at 8:02 AM, Steve Varnau <[email protected]> > wrote: > > > An update on jenkins automated testing. > > > > The test jobs for the release2.1 branch have now switched over to using > > the python-installer instead of the bash installer. When recent pyinstaller > > changes have been merged over to the master branch, then those tests > can be > > switched over as well. > > > > Thanks to Eason for quickly addressing the changes needed for the test > > environment. > > > > --Steve > > > >
