Gradle Enterprise for JHipster Lite

[Frederik Hahne]

Hi everyone,

It was nice to meet you yesterday. Coming back to our gradle enterprise instance. I see at least two ways to put it to better use.

* integrate it into the jhipster gradle sample (in fact I always wanted to do that, but didn't, sorry for that) --> we will have build scans at least for every release, so we will see improvements (or getting worse, who knows)

* integrate it into the general jhipster lite build, which is a maven project,  but we will have build scans, and for everyone who would like to have it the build cache too.

what do you think?

For the putting atomic jar/testcontainers to a higher sponsorship tear, we might use it in jhipster lite, but there is only one integration test using testcontainers right now. About the jhipster classic ci (which uses docker a lot) I am not sure we use testcontainers for everything, but it might be worth a try if we have a jhipster account/credentials. But I have never used testcontainers cloud in ci yet, so not sure how much we would have to change.

best regards

Frederik

[Pascal GRIMAUD]

Hello,

The JHLite took approximatively 4min15 to build, using the cache from GitHub.

But if you think it can be improved by the Gradle Enterprise, yes let's go ahead.

It's always better to have the fastest CI as possible :-)

For testcontainers in JHLite, I need to have a look but some options use testcontainers, like PostgreSQL, Kafka, Cassandra, Keycloak... So it can help here too.

Pascal

--
You received this message because you are subscribed to the Google Groups "JHipster dev team" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jhipster-dev...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jhipster-dev/CACh2FPQrW8Ek5QjKemP65d%2BHA63Tzyo_U5zqUNghj5N1MTAQ%2Bg%40mail.gmail.com.

[Frederik Hahne]

Just realized yesterday we don't have the required license to use maven with our Gradle enterprise instance. Therfore I will first try to get it into the sample app's ci.