You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@fineract.apache.org by "Adam Monsen (Jira)" <ji...@apache.org> on 2025/07/17 19:42:00 UTC
[jira] [Updated] (FINERACT-2328) improve local build+test on dev computers
[ https://issues.apache.org/jira/browse/FINERACT-2328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Adam Monsen updated FINERACT-2328:
----------------------------------
Description:
The authoritative build+test CI pipeline can only run on GitHub. I propose two improvements:
# make it possible for devs to again run builds (including all tests) locally
# make it _easy_ for devs to again run builds (including all tests) locally
The first is [required by the ASF|https://www.apache.org/legal/release-policy.html#owned-controlled-hardware], but is also a good idea and best practice. Ideally our builds would be reproducible (a good stretch goal to strive for).
The second improvement supports the first. The easier it is for devs to build on their own, the more it'll occur. I'd expect to see simple gradle build tasks like "build", "test", "doc", and not need to add any "-x :slow-stuff" or "-x :broken-stuff" exceptions. It seems reasonable we'd separate different kinds of tests since Fineract has so many, but the goal of this second improvement is that they're easier to run.
Note this ticket says nothing about the execution time for the build, only that it's possible and easy for devs to run it on their own computers.
These can be broken up into separate tickets if/as necessary.
was:
The authoritative build+test CI pipeline is currently only possible on GitHub. I propose two improvements:
# make it possible for devs to again run builds (including all tests) locally
# make it _easy_ for devs to again run builds (including all tests) locally
The first one is [required by the ASF|https://www.apache.org/legal/release-policy.html#owned-controlled-hardware], but is also a good idea and best practice. Our builds are ideally reproducible.
The second simply enables and encourages the first. The easier it is, the more it'll occur. I'd expect to see simple gradle build tasks like "build", "test", "doc", and not need to add any "-x :slow-stuff" or "-x :broken-stuff" exceptions. It seems reasonable we'd separate different kinds of tests since Fineract has so many, but the goal of this second improvement is that they're easier to run.
These can be broken up into separate tickets if/as necessary.
> improve local build+test on dev computers
> -----------------------------------------
>
> Key: FINERACT-2328
> URL: https://issues.apache.org/jira/browse/FINERACT-2328
> Project: Apache Fineract
> Issue Type: Task
> Reporter: Adam Monsen
> Priority: Major
> Fix For: 1.13.0
>
>
> The authoritative build+test CI pipeline can only run on GitHub. I propose two improvements:
> # make it possible for devs to again run builds (including all tests) locally
> # make it _easy_ for devs to again run builds (including all tests) locally
> The first is [required by the ASF|https://www.apache.org/legal/release-policy.html#owned-controlled-hardware], but is also a good idea and best practice. Ideally our builds would be reproducible (a good stretch goal to strive for).
> The second improvement supports the first. The easier it is for devs to build on their own, the more it'll occur. I'd expect to see simple gradle build tasks like "build", "test", "doc", and not need to add any "-x :slow-stuff" or "-x :broken-stuff" exceptions. It seems reasonable we'd separate different kinds of tests since Fineract has so many, but the goal of this second improvement is that they're easier to run.
> Note this ticket says nothing about the execution time for the build, only that it's possible and easy for devs to run it on their own computers.
> These can be broken up into separate tickets if/as necessary.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)