[ 
https://issues.apache.org/jira/browse/BEAM-3250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16425894#comment-16425894
 ] 

Alex Amato commented on BEAM-3250:
----------------------------------

FWIW, here is what I learned yesterday. 

While looking to migrate:

job_beam_PostCommit_Java_MavenInstall.groovy

to a PostCommit file, i.e.

job_beam_PostCommit_Java_GradleBuild.groovy

I discovered that the gradle precommit test was actually running most of the 
integration tests

beam_PreCommit_Java_GradleBuild

It was not running the apexRunnerTests, due to a bug listed in the 
examples/build.gradle file (which has a few functions to invoke all the 
integration test variants).

Maven tagged tests as integration-test but gradle does noto, so we need to 
define functions/tasks in gradle to pick out the integration tests and just run 
those in postcommit.

 

Though I think for this one, we can just make a postCommit file which does 
basically the same thing as 

beam_PreCommit_Java_GradleBuild, which appears to be running integration tests 
which Maven was doing before. 

I believe Dan sent a PR for one of the PostCommit tests out yesterday.

> Migrate ValidatesRunner Jenkins PostCommits to Gradle
> -----------------------------------------------------
>
>                 Key: BEAM-3250
>                 URL: https://issues.apache.org/jira/browse/BEAM-3250
>             Project: Beam
>          Issue Type: Sub-task
>          Components: build-system, testing
>            Reporter: Luke Cwik
>            Assignee: Henning Rohde
>            Priority: Major
>          Time Spent: 40m
>  Remaining Estimate: 0h
>
> Update these targets to execute ValidatesRunner tests: 
> https://github.com/apache/beam/search?l=Groovy&q=ValidatesRunner&type=&utf8=%E2%9C%93



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to