You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@beam.apache.org by Jean-Baptiste Onofré <jb...@nanthrax.net> on 2016/04/05 07:50:33 UTC

[PROPOSAL] Nightly builds by Jenkins

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é
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

Re: [PROPOSAL] Nightly builds by Jenkins

Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
It sounds good.

As the artifacts location will move, and regarding the default 
"discard/deletion" policy on the snapshot repo, I think it's OK.

Thanks !
Regards
JB

On 04/09/2016 03:04 AM, Davor Bonaci wrote:
> This is already done, since it was trivial and INFRA was super-fast  ;)
>
> I'll send a separate email with usage instructions.
>
> On Fri, Apr 8, 2016 at 9:59 AM, Davor Bonaci <da...@google.com> wrote:
>
>> 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é <jb...@nanthrax.net>
>> 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é
>>> jbonofre@apache.org
>>> http://blog.nanthrax.net
>>> Talend - http://www.talend.com
>>>
>>
>>
>

-- 
Jean-Baptiste Onofré
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

Re: [PROPOSAL] Nightly builds by Jenkins

Posted by Davor Bonaci <da...@google.com.INVALID>.
This is already done, since it was trivial and INFRA was super-fast  ;)

I'll send a separate email with usage instructions.

On Fri, Apr 8, 2016 at 9:59 AM, Davor Bonaci <da...@google.com> wrote:

> 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é <jb...@nanthrax.net>
> 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é
>> jbonofre@apache.org
>> http://blog.nanthrax.net
>> Talend - http://www.talend.com
>>
>
>

Re: [PROPOSAL] Nightly builds by Jenkins

Posted by Davor Bonaci <da...@google.com.INVALID>.
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é <jb...@nanthrax.net>
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é
> jbonofre@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>

Re: [PROPOSAL] Nightly builds by Jenkins

Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
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é
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

Re: [PROPOSAL] Nightly builds by Jenkins

Posted by Davor Bonaci <da...@google.com.INVALID>.
Nice to see uniform opinion here ;)

Pre-commit and post-commit (beam_MavenVerify) should also take care of code
coverage reporting.
In addition to the nightly build, we had planned to use Jenkins for release
automation (e.g., deployment of release candidates, version number
management, branching, etc.).

In terms of Jenkins jobs, lots more to come.

On Tue, Apr 5, 2016 at 9:35 AM, Kenneth Knowles <kl...@google.com.invalid>
wrote:

> On Tue, Apr 5, 2016 at 1:57 AM, Maximilian Michels <mx...@apache.org> wrote:
> >
> > - Test coverage of pull requests (beam_PreCommit)
> > - Test coverage of the master and all other branches (beam_MavenVerify)
> > - A daily job that deploys artifacts to the snapshot repository
> > (beam_Nightly)
> >
>
> I like this. Everything here is very simple to understand and has a clear
> purpose.
>
> Kenn
>

Re: [PROPOSAL] Nightly builds by Jenkins

Posted by Kenneth Knowles <kl...@google.com.INVALID>.
On Tue, Apr 5, 2016 at 1:57 AM, Maximilian Michels <mx...@apache.org> wrote:
>
> - Test coverage of pull requests (beam_PreCommit)
> - Test coverage of the master and all other branches (beam_MavenVerify)
> - A daily job that deploys artifacts to the snapshot repository
> (beam_Nightly)
>

I like this. Everything here is very simple to understand and has a clear
purpose.

Kenn

Re: [PROPOSAL] Nightly builds by Jenkins

Posted by Maximilian Michels <mx...@apache.org>.
Hey JB,

I would also propose three Jenkins jobs (apart from the Cloud Dataflow tests):

- Test coverage of pull requests (beam_PreCommit)
- Test coverage of the master and all other branches (beam_MavenVerify)
- A daily job that deploys artifacts to the snapshot repository (beam_Nightly)

Keeping the last two separate makes it easier to change the deployment
of snapshots. Daily deployment should be enough. If we ever want to
deploy more frequently, we can easily adjust the schedule of the
build. In addition, we can identify problems regarding the deployment
more easily and prevent breakage of the test execution of the
development branches.

Best,
Max

On Tue, Apr 5, 2016 at 9:57 AM, Jason Kuster
<ja...@google.com.invalid> wrote:
> Hey JB,
>
> Just want to clarify - do you mean that beam_nightly would continue to run
> on the schedule it currently has (SCM poll/hourly), plus one run at
> midnight?
>
> I think Dan's question centers around whether beam_nightly build would just
> run once every 24h. We want our postsubmit coverage to run more often than
> that is my impression. Doing a deploy every time the SCM poll returns some
> changes seems like an aggressive schedule to me, but I welcome your
> thoughts there. Otherwise we could keep beam_mavenverify running on the scm
> poll/hourly schedule and add the beam_nightly target which just does a
> single deploy every 24h.
>
> Thanks,
>
> Jason
>
> On Tue, Apr 5, 2016 at 12:41 AM, Jean-Baptiste Onofré <jb...@nanthrax.net>
> wrote:
>
>> Hi Dan,
>>
>> you can have both mvn clean deploy and mvn clean verify, but IMHO, the
>> first already covers the second ;)
>>
>> So, I think mvn clean deploy is fine instead of clean verify.
>>
>> WDYT ?
>>
>> Regards
>> JB
>>
>>
>> On 04/05/2016 08:05 AM, Dan Halperin wrote:
>>
>>> I am completely behind producing nightly jars.
>>>
>>> But, I don't think that `beam_MavenVerify` is completely redundant -- I
>>> was
>>> under the impression it was our main post-submit coverage. Is that wrong?
>>>
>>> If I'm not wrong, then I think this should simply be a fourth Jira target
>>> that runs every 24h.
>>>
>>> On Mon, Apr 4, 2016 at 10:50 PM, Jean-Baptiste Onofré <jb...@nanthrax.net>
>>> 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é
>>>> jbonofre@apache.org
>>>> http://blog.nanthrax.net
>>>> Talend - http://www.talend.com
>>>>
>>>>
>>>
>> --
>> Jean-Baptiste Onofré
>> jbonofre@apache.org
>> http://blog.nanthrax.net
>> Talend - http://www.talend.com
>>
>
>
>
> --
> -------
> Jason Kuster
> Apache Beam (Incubating) / Google Cloud Dataflow

Re: [PROPOSAL] Nightly builds by Jenkins

Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Hi Jason,

Oh ok ;)

I would say:
- mvn clean verify for each scm change
- mvn clean deploy systematically at midnight

So, two jobs on Jenkins.

My $0.01

Regards
JB

On 04/05/2016 09:57 AM, Jason Kuster wrote:
> Hey JB,
>
> Just want to clarify - do you mean that beam_nightly would continue to run
> on the schedule it currently has (SCM poll/hourly), plus one run at
> midnight?
>
> I think Dan's question centers around whether beam_nightly build would just
> run once every 24h. We want our postsubmit coverage to run more often than
> that is my impression. Doing a deploy every time the SCM poll returns some
> changes seems like an aggressive schedule to me, but I welcome your
> thoughts there. Otherwise we could keep beam_mavenverify running on the scm
> poll/hourly schedule and add the beam_nightly target which just does a
> single deploy every 24h.
>
> Thanks,
>
> Jason
>
> On Tue, Apr 5, 2016 at 12:41 AM, Jean-Baptiste Onofré <jb...@nanthrax.net>
> wrote:
>
>> Hi Dan,
>>
>> you can have both mvn clean deploy and mvn clean verify, but IMHO, the
>> first already covers the second ;)
>>
>> So, I think mvn clean deploy is fine instead of clean verify.
>>
>> WDYT ?
>>
>> Regards
>> JB
>>
>>
>> On 04/05/2016 08:05 AM, Dan Halperin wrote:
>>
>>> I am completely behind producing nightly jars.
>>>
>>> But, I don't think that `beam_MavenVerify` is completely redundant -- I
>>> was
>>> under the impression it was our main post-submit coverage. Is that wrong?
>>>
>>> If I'm not wrong, then I think this should simply be a fourth Jira target
>>> that runs every 24h.
>>>
>>> On Mon, Apr 4, 2016 at 10:50 PM, Jean-Baptiste Onofré <jb...@nanthrax.net>
>>> 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é
>>>> jbonofre@apache.org
>>>> http://blog.nanthrax.net
>>>> Talend - http://www.talend.com
>>>>
>>>>
>>>
>> --
>> Jean-Baptiste Onofré
>> jbonofre@apache.org
>> http://blog.nanthrax.net
>> Talend - http://www.talend.com
>>
>
>
>

-- 
Jean-Baptiste Onofré
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

Re: [PROPOSAL] Nightly builds by Jenkins

Posted by Robert Bradshaw <ro...@google.com.INVALID>.
On Tue, Apr 5, 2016 at 12:57 AM, Jason Kuster
<ja...@google.com.invalid> wrote:
> Hey JB,
>
> Just want to clarify - do you mean that beam_nightly would continue to run
> on the schedule it currently has (SCM poll/hourly), plus one run at
> midnight?
>
> I think Dan's question centers around whether beam_nightly build would just
> run once every 24h. We want our postsubmit coverage to run more often than
> that is my impression. Doing a deploy every time the SCM poll returns some
> changes seems like an aggressive schedule to me, but I welcome your
> thoughts there. Otherwise we could keep beam_mavenverify running on the scm
> poll/hourly schedule and add the beam_nightly target which just does a
> single deploy every 24h.

Unless it's too expensive, I would suggest we do a mvn verify every
time the branch changes (plus at some regular interval). The nightly
target would deploy just at midnight (and I don't see much value,
actually it's probably counter-productive, to deploy more often than
that).

> On Tue, Apr 5, 2016 at 12:41 AM, Jean-Baptiste Onofré <jb...@nanthrax.net>
> wrote:
>
>> Hi Dan,
>>
>> you can have both mvn clean deploy and mvn clean verify, but IMHO, the
>> first already covers the second ;)
>>
>> So, I think mvn clean deploy is fine instead of clean verify.
>>
>> WDYT ?
>>
>> Regards
>> JB
>>
>>
>> On 04/05/2016 08:05 AM, Dan Halperin wrote:
>>
>>> I am completely behind producing nightly jars.
>>>
>>> But, I don't think that `beam_MavenVerify` is completely redundant -- I
>>> was
>>> under the impression it was our main post-submit coverage. Is that wrong?
>>>
>>> If I'm not wrong, then I think this should simply be a fourth Jira target
>>> that runs every 24h.
>>>
>>> On Mon, Apr 4, 2016 at 10:50 PM, Jean-Baptiste Onofré <jb...@nanthrax.net>
>>> 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é
>>>> jbonofre@apache.org
>>>> http://blog.nanthrax.net
>>>> Talend - http://www.talend.com
>>>>
>>>>
>>>
>> --
>> Jean-Baptiste Onofré
>> jbonofre@apache.org
>> http://blog.nanthrax.net
>> Talend - http://www.talend.com
>>
>
>
>
> --
> -------
> Jason Kuster
> Apache Beam (Incubating) / Google Cloud Dataflow

Re: [PROPOSAL] Nightly builds by Jenkins

Posted by Jason Kuster <ja...@google.com.INVALID>.
Hey JB,

Just want to clarify - do you mean that beam_nightly would continue to run
on the schedule it currently has (SCM poll/hourly), plus one run at
midnight?

I think Dan's question centers around whether beam_nightly build would just
run once every 24h. We want our postsubmit coverage to run more often than
that is my impression. Doing a deploy every time the SCM poll returns some
changes seems like an aggressive schedule to me, but I welcome your
thoughts there. Otherwise we could keep beam_mavenverify running on the scm
poll/hourly schedule and add the beam_nightly target which just does a
single deploy every 24h.

Thanks,

Jason

On Tue, Apr 5, 2016 at 12:41 AM, Jean-Baptiste Onofré <jb...@nanthrax.net>
wrote:

> Hi Dan,
>
> you can have both mvn clean deploy and mvn clean verify, but IMHO, the
> first already covers the second ;)
>
> So, I think mvn clean deploy is fine instead of clean verify.
>
> WDYT ?
>
> Regards
> JB
>
>
> On 04/05/2016 08:05 AM, Dan Halperin wrote:
>
>> I am completely behind producing nightly jars.
>>
>> But, I don't think that `beam_MavenVerify` is completely redundant -- I
>> was
>> under the impression it was our main post-submit coverage. Is that wrong?
>>
>> If I'm not wrong, then I think this should simply be a fourth Jira target
>> that runs every 24h.
>>
>> On Mon, Apr 4, 2016 at 10:50 PM, Jean-Baptiste Onofré <jb...@nanthrax.net>
>> 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é
>>> jbonofre@apache.org
>>> http://blog.nanthrax.net
>>> Talend - http://www.talend.com
>>>
>>>
>>
> --
> Jean-Baptiste Onofré
> jbonofre@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>



-- 
-------
Jason Kuster
Apache Beam (Incubating) / Google Cloud Dataflow

Re: [PROPOSAL] Nightly builds by Jenkins

Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Hi Dan,

you can have both mvn clean deploy and mvn clean verify, but IMHO, the 
first already covers the second ;)

So, I think mvn clean deploy is fine instead of clean verify.

WDYT ?

Regards
JB

On 04/05/2016 08:05 AM, Dan Halperin wrote:
> I am completely behind producing nightly jars.
>
> But, I don't think that `beam_MavenVerify` is completely redundant -- I was
> under the impression it was our main post-submit coverage. Is that wrong?
>
> If I'm not wrong, then I think this should simply be a fourth Jira target
> that runs every 24h.
>
> On Mon, Apr 4, 2016 at 10:50 PM, Jean-Baptiste Onofré <jb...@nanthrax.net>
> 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é
>> jbonofre@apache.org
>> http://blog.nanthrax.net
>> Talend - http://www.talend.com
>>
>

-- 
Jean-Baptiste Onofré
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

Re: [PROPOSAL] Nightly builds by Jenkins

Posted by Dan Halperin <dh...@google.com.INVALID>.
I am completely behind producing nightly jars.

But, I don't think that `beam_MavenVerify` is completely redundant -- I was
under the impression it was our main post-submit coverage. Is that wrong?

If I'm not wrong, then I think this should simply be a fourth Jira target
that runs every 24h.

On Mon, Apr 4, 2016 at 10:50 PM, Jean-Baptiste Onofré <jb...@nanthrax.net>
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é
> jbonofre@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>