[
https://issues.apache.org/jira/browse/BEAM-4014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16427807#comment-16427807
]
Thomas Groh commented on BEAM-4014:
-----------------------------------
There are a couple of difficulties here - the primary one is that with the
existing Maven test, we execute all of the dependencies of the Core SDK and
execute all the integration tests that are part of the classpath. I haven't
found an obvious way from within Gradle to, within a top-level module,
aggregate all of the produced artifacts (matching against a string, ideally,
like {{"**/*IT.java"}}, and run a single execution against them.
My belief is that this likely requires each module that declares integration
tests to declare an "integrationTest" task, which executes its integration test
on some subset of runners where such a test is appropriate (beginning with only
the Dataflow Runner), and have the top-level {{postCommit}} task depend on all
of them. The actual jenkins task is then executing that postCommit, as is done
in the gradle precommits.
The actual name {{MavenInstall}} is also generically misleading - this is an
execution of the Java ITs on the Dataflow Runner, not a validation that
{{MavenInstall}} produces the proper artifacts.
> Migrate MavenInstall Jenkins PostCommits to Gradle
> --------------------------------------------------
>
> Key: BEAM-4014
> URL: https://issues.apache.org/jira/browse/BEAM-4014
> Project: Beam
> Issue Type: Sub-task
> Components: build-system, testing
> Reporter: Henning Rohde
> Assignee: Thomas Groh
> Priority: Major
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
