I was hoping we could get the nightly build even before that point. INFRA-11623 is asking for Nexus access for Beam.
On Fri, Apr 8, 2016 at 9:03 AM, Jean-Baptiste Onofré <[email protected]> wrote: > As it seems that we have an agreement, once the renaming task is complete, > I will setup a nightly build on Jenkins. > > Thanks ! > Regards > JB > > > On 04/05/2016 07:50 AM, Jean-Baptiste Onofré wrote: > >> Hi beamers, >> >> Now, on Jenkins, we have three jobs: >> >> - beam_PreCommit does a mvn clean verify for each opened PR >> - beam_MavenVerify does a mvn clean verify on master branch >> - beam_RunnableOnService_GoogleCloudDataflow does a mvn clean verify >> -PDataflowPipelineTests on master branch >> >> As discussed last week, Davor and I are working on renaming (especially >> package). >> >> Once this renaming done (it should take a week or so), I propose to >> change beam_MavenVerify as beam_Nightly: it will do a mvn clean deploy >> deploying SNAPSHOTs on the Apache SNAPSHOT repo (deploy phase includes >> verify and test of course) with a schedule every night and SCM change. >> >> It will allow people to test and try beam without building. >> >> Thoughts ? >> >> Regards >> JB >> > > -- > Jean-Baptiste Onofré > [email protected] > http://blog.nanthrax.net > Talend - http://www.talend.com >
