Following this jhipster/generator-jhipster#9484 (comment)

The problem is the keycloak.yml file is not generated any more for microservices.
So we can't start a microservice with OAuth2, alone. It needed to be a Gateway.

As a temporary fix, I disabled the run. See my commit: 5b8f125

It could be tested back as soon as I finish the multi app, using JDL:

• generate 2 or 3 applications using JDL
• package and create Docker image
• start the full stack, using docker-compose with app.yml file

Protractor is deprecated, our cypress support is good now.
We should migrate every test to cypress.

While the blueprints are getting more and more popular and performing, they lack test coverage: some of them cover almost as much as the main generator and it would be great to implement a way to expand the test coverage to these blueprints, here are some ideas:

• Have another Azure organisation for each blueprints (Kotlin ? Vuejs?) and "fork" this repo.
• Add some more daily builds configuration as we still have some "time left" each day to run some more configurations

Related Issues/PR:

• vuejs
• #10

Pinging lord and saviour @pascalgrimaud for input

see this

Disabled at f5dbe94

The integration tests are too flatky.
See :

• https://github.com/hipster-labs/jhipster-daily-builds/actions?query=workflow%3A%22Angular+Maven+NoSQL%22
• https://github.com/hipster-labs/jhipster-daily-builds/actions?query=workflow%3A%22Angular+Gradle+NoSQL%22
• https://github.com/hipster-labs/jhipster-daily-builds/actions?query=workflow%3A%22React+Maven+NoSQL%22
• https://github.com/hipster-labs/jhipster-daily-builds/actions?query=workflow%3A%22React+Gradle+NoSQL%22

cc @tchlyah -> as you're our main contributor on Couchbase
cc @SudharakaP -> as I know you already spent a lot of time on this

Asked by @pmverma here: jhipster/generator-jhipster#10662 (comment)

I'll try to add this pipeline when possible
@Hawkurane has the permission to do it too

I can add more admins if needed. Just ask !

Disabled at 4be3737

cc @Hawkurane : FYI, I disabled it. I think it is useless to let the build running if it failed.

Following this jhipster/generator-jhipster#9674 (comment)
It would be 6 builds :

• Angular + Maven + JWT + no database
• Angular + Maven + Session + no database
• Angular + Maven + OAuth2 + no database
• React + Gradle + JWT + no database
• React + Gradle + Session + no database
• React + Gradle + OAuth2 + no database

For example, see @deepu105's sample JDL file : https://gist.github.com/deepu105/8e568eb7b5b5e3c00af0fdf3d2cf71ba
This would be really convenient to describe a full microservice architecture and for easily reproducing locally.

Currently, the windows build workflows returns with

Error when evaluating 'runs-on' for job 'applications'. Unexpected value ''

It seems, it has trouble finding the value 'windows-latest' for the runs-on parameter.
Associated documentation: https://help.github.com/en/actions/reference/virtual-environments-for-github-hosted-runners

Similar to NPM but with Yarn

This is a follow-up to add headless mode for e2e tests but for daily-builds. Only JDLMS Builds should be affected since the other scenarios are relying on the main generator repo's scripts.

Following this jhipster/jhipster-kotlin#138 (comment)

Hello,
how can we configure watchtower with jhipster?
We run our jhipster application executing by docker-composite app.yml file.

Can we configure watchtower to automatizate the pull and run of the image?
Thanks,
Francesco

• need to switch to JDK11 by default
• add builds for JDK8

Add to daily builds workflows:

on: 
  workflow_dispatch:

Reference https://github.blog/changelog/2020-07-06-github-actions-manual-triggers-with-workflow_dispatch/

It would be great to have reactive configuration for neo4j in our matrix. I will take care of it.

It caught my attention that the windows daily build is failing for ngx-mongodb-kafka-cucumber for a while with the error;

[ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 6.412 s <<< FAILURE! - in io.github.jhipster.sample.web.rest.SampleMongoKafkaKafkaResourceIT
[ERROR] io.github.jhipster.sample.web.rest.SampleMongoKafkaKafkaResourceIT  Time elapsed: 6.412 s  <<< ERROR!
org.testcontainers.containers.ContainerLaunchException: Container startup failed
	at io.github.jhipster.sample.web.rest.SampleMongoKafkaKafkaResourceIT.startTestcontainer(SampleMongoKafkaKafkaResourceIT.java:46)
	at io.github.jhipster.sample.web.rest.SampleMongoKafkaKafkaResourceIT.startServer(SampleMongoKafkaKafkaResourceIT.java:37)
Caused by: org.testcontainers.containers.ContainerFetchException: Can't get Docker image: RemoteDockerImage(imageName=confluentinc/cp-kafka:5.5.1, imagePullPolicy=DefaultPullPolicy())
	at io.github.jhipster.sample.web.rest.SampleMongoKafkaKafkaResourceIT.startTestcontainer(SampleMongoKafkaKafkaResourceIT.java:46)
	at io.github.jhipster.sample.web.rest.SampleMongoKafkaKafkaResourceIT.startServer(SampleMongoKafkaKafkaResourceIT.java:37)
Caused by: java.lang.IllegalStateException: Could not find a valid Docker environment. Please see logs and check configuration
	at io.github.jhipster.sample.web.rest.SampleMongoKafkaKafkaResourceIT.startTestcontainer(SampleMongoKafkaKafkaResourceIT.java:46)
	at io.github.jhipster.sample.web.rest.SampleMongoKafkaKafkaResourceIT.startServer(SampleMongoKafkaKafkaResourceIT.java:37)

[INFO] Running io.github.jhipster.sample.web.rest.UserJWTControllerIT

Sample Build Failure: https://github.com/hipster-labs/jhipster-daily-builds/runs/1111112469?check_suite_focus=true

Now that protractor is considered deprecrated in a JHipster application, we should change from protractor e2e tests to cypress ones.

OAuth2 + Protractor is not stable enough: too much random failures
So it will be better to extract these builds in dedicate file

I was looking into failing builds after the recent react migrations jhipster/generator-jhipster#15191 and jhipster/generator-jhipster#15106 and found that there are many other failing builds as well with weird errors

Many failures seems to be during e2e tests. The angular protractor e2e tests are also failing and the above migrations havent touched those so it needs investigation. Also the React e2e were fixed in recent commits but the repo here seems to use old code anyway. @pascalgrimaud is there some sort of cache here?

Overall I might need more help here @pascalgrimaud @DanielFran @mshima @SudharakaP

Tried to install the Jhipster IDE 2.3.5 from Spring Tool Suite 4
(Version: 4.10.0.RELEASE,Build Id: 202103111225) eclipse market place.
But encountered problem .
Please see the details:

An error occurred while collecting items to be installed
session context was:(profile=DefaultProfile, phase=org.eclipse.equinox.internal.p2.engine.phases.Collect, operand=, action=).
Artifact not found: osgi.bundle,com.google.inject,3.0.0.v201605172100.
Artifact not found: osgi.bundle,org.apache.commons.cli,1.4.0.v20200417-1444.
Artifact not found: osgi.bundle,org.eclipse.emf,2.8.0.v20180706-1146.
Artifact not found: osgi.bundle,org.eclipse.emf.codegen.ecore,2.25.0.v20201231-0738.
Artifact not found: osgi.bundle,org.eclipse.emf.ecore.editor,2.17.0.v20190528-0725.
Artifact not found: osgi.bundle,org.eclipse.emf.mwe.core,1.6.1.v20210218-2134.
Artifact not found: osgi.bundle,org.eclipse.emf.mwe.utils,1.6.1.v20210218-2134.
Artifact not found: osgi.bundle,org.eclipse.emf.mwe2.lib,2.12.1.v20210218-2134.
Artifact not found: osgi.bundle,org.eclipse.emf.mwe2.runtime,2.12.1.v20210218-2134.

Disabled at f5dbe94

Waiting to be fixed in main-generator JHipster.
cc @atomfrede -> when it's fixed, we can reactivate it