... the performance issues stem from "dependsOn"... and similar... there
are also neat features in Gradle where you can precompile pretty much all
of the build script (and "configuration" cache it) which would boost the
build process by a lot (disclosure: I am using this technique in projects
with
I believe many of our issues stem from our current Gradle build being
overly complex. One of my main concerns with Gradle is that it allows
customization to evolve completely out of control. Following this
principle, I would be opposed to adding new elements to our build.
Instead, I’d like to see
Hello,
What about adding observability to the building process? In this way we can
have information about the root causes of the issues during the building
time.
A OSS suggestion:
https://github.com/craigatk/opentelemetry-gradle-plugin
Regards
Victor
El dom, 1 sept 2024 a las 10:06, James Dai
+1 agree
How do we tackle this ?
On Sun, Sep 1, 2024 at 7:49 AM Avik Ganguly wrote:
> Still, when eg. 2 tests fail out of the 1100+ on a Github build, it's a
>> horror to find out which ones failed, and our best bet is to text-search
>> for "FAILED" in the 17000+ lines of output.
>
> +1
>
> Ite
>
> Still, when eg. 2 tests fail out of the 1100+ on a Github build, it's a
> horror to find out which ones failed, and our best bet is to text-search
> for "FAILED" in the 17000+ lines of output.
+1
Items like this should be high priority in CI improvements epic. The
overall failed test history,
Kristof,
... great overview, so first: thanks for that. Some notes...
Repeatable builds: we should consider this as a major bug and not just
"gloss over" it by executing the build multiple times... stuff like this
should halt all current development on other features and everyone (or at
least one
Hi all,
After working with Fineract for some months now, I collected several issues
related to the Gradle build system we have in place. I categorized my pain
points, and would like to initiate a discussion on the topic with the
community. My usage scenarios include building locally with IntelliJ+