As we are working on fixing this issue, some extra parameters may help the build to get bit quicker on your machine.
using -xjavadoc -xdoc Eg: ./gradlew clean build -Dskip.tests=true -xjavadoc -xdocs BUILD SUCCESSFUL Total time: 2 mins 2.729 secs Also, I think as Jason mentioned that the slow down is due to full product download for session state tests. LuceneSearchWithRollingUpgradeDUnit tests were added in July. Please do correct me if I am wrong. Regards Nabarun On Tue, Sep 12, 2017 at 11:47 AM Alexander Murmann <amurm...@pivotal.io> wrote: > Could we make it so that these tests for now are only run as part of > pre-checkin till we got this ironed out and then revisit this? > > On Tue, Sep 12, 2017 at 8:32 AM, Bruce Schuchardt <bschucha...@pivotal.io> > wrote: > > > The geode-old-versions module was originally created to pull in old > > version jar files into your gradle cache. This happened only once and > you > > were good to go. I don't think that part should be backed out as it has > > minimal impact and is not affecting build time. > > > > The recent changes for lucene testing seem to be pulling in full > > installations of old versions and these are deleted as part of the > "clean" > > gradle task. That's causing them to be downloaded again each time you > do a > > clean&build. Dan put changes in place so that the files aren't > downloaded > > again if you build without cleaning but clearly more needs to be done in > > this area. > > > > > > > > On 9/11/17 11:23 AM, Jacob Barrett wrote: > > > >> Agreed, integration tests should not be part of the build process. This > >> is clearly an integration test. > >> > >> On Sep 11, 2017, at 11:00 AM, Udo Kohlmeyer <u...@apache.org> wrote: > >>> > >>> Hi there, > >>> > >>> With a recent addition to the build scripts, to test lucene backwards > >>> compatibility, a step was added to download a previous version of > GEODE. > >>> > >>> This is causing longer build times now, which is a real distraction. In > >>> cases where one would like to work on a branch, rebase that on develop > and > >>> merge that, this step becomes a real time hog. > >>> > >>> I request that we remove this default behavior from a clean build until > >>> we have a better solution to this issue. > >>> > >>> I also believe that if anyone wants to add behavior like this into the > >>> default build, that it at least is discussed on the dev list before > >>> implementing this. > >>> > >>> --Udo > >>> > >>> > > >
