build/devops

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

build/devops

cw7k
Hi, a full mvn install takes about 2-2.5 hours.  Does the Flink team run the full testsuite on every dev pull request, or use a main dev branch that gets the full test periodically?  Or a different method?  The 2 hours can be a drag when one team needs another's changes and each attempt at passing requires a wait of 2+ hours.
Reply | Threaded
Open this post in threaded view
|

Re: build/devops

Chesnay Schepler-3
Generally we run the full test suite on travis for every pull request. I
would guess that dev working on some part
only run certain tests locally though.

On 08.02.2018 01:06, cw7k wrote:
> Hi, a full mvn install takes about 2-2.5 hours.  Does the Flink team run the full testsuite on every dev pull request, or use a main dev branch that gets the full test periodically?  Or a different method?  The 2 hours can be a drag when one team needs another's changes and each attempt at passing requires a wait of 2+ hours.


Reply | Threaded
Open this post in threaded view
|

Re: build/devops

Fabian Hueske-2
A full build incl. tests takes on my machine about 40 to 50 mins (if all
dependencies are locally cached).
Locally, I only run tests on the modules that I modified as Chesnay said.

2018-02-08 8:05 GMT+01:00 Chesnay Schepler <[hidden email]>:

> Generally we run the full test suite on travis for every pull request. I
> would guess that dev working on some part
> only run certain tests locally though.
>
>
> On 08.02.2018 01:06, cw7k wrote:
>
>> Hi, a full mvn install takes about 2-2.5 hours.  Does the Flink team run
>> the full testsuite on every dev pull request, or use a main dev branch that
>> gets the full test periodically?  Or a different method?  The 2 hours can
>> be a drag when one team needs another's changes and each attempt at passing
>> requires a wait of 2+ hours.
>>
>
>
>