[
https://issues.apache.org/jira/browse/FINERACT-1226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17217971#comment-17217971
]
Aleksandar Vidakovic commented on FINERACT-1226:
------------------------------------------------
[~vorburger] How about just doing a "./gradlew build integrationTest" (just for
shortness without the other parameters)? That will catch every module no matter
if it's Java, Kotlin, Groovy, generated, just tests or documentation (later).
The "integrationTest" task is very specific and kicks only in when a module has
those tests... which will be probably always be only one. I think "build" is
our friend here.
> Travis CI does not actually build new multi module project structure
> --------------------------------------------------------------------
>
> Key: FINERACT-1226
> URL: https://issues.apache.org/jira/browse/FINERACT-1226
> Project: Apache Fineract
> Issue Type: Sub-task
> Reporter: Michael Vorburger
> Assignee: Michael Vorburger
> Priority: Major
> Fix For: 1.5.0
>
>
> https://github.com/apache/fineract/pull/1446 broke the build, but we didn't
> notice it.
> https://github.com/apache/fineract/pull/1448 manually fixes it.
> This shouldn't have happened, and it seemed curious to me that it did, so I
> had a look:
> It's because in our
> https://github.com/apache/fineract/blob/develop/.travis.yml we, currently,
> only:
> {{./gradlew --console=plain -PautomatedBuild=true licenseMain licenseTest
> licenseIntegrationTest check && ./gradlew --console=plain
> -PautomatedBuild=true integrationTest --fail-fast}}
> and this doesn't actually build {{fineract-client/}}, that's why!
> [~aleks] what do you think would be a better Gradle task goal to build in CI,
> to cover everything? We probably shouldn't list {{:fineract-client}}, as we
> will be adding more modules, so something more general...
> [~ptuomola] FYI
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
