-
-
Notifications
You must be signed in to change notification settings - Fork 4.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fixes daily-build regressions related to npm scripts migration #18780
Conversation
generators/server/index.js
Outdated
@@ -459,6 +459,11 @@ module.exports = class JHipsterServerGenerator extends BaseBlueprintGenerator { | |||
'docker:db:await': `echo "Waiting for Couchbase to start" && wait-on -t ${WAIT_TIMEOUT} http-get://localhost:8091/ui/index.html && sleep 30 && echo "Couchbase started"`, | |||
}); | |||
} | |||
if (prodDatabaseType === MYSQL) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I guess that now we should also add this line if devDatabaseType is Mysql too.
Maybe a liveliness probe in the docker-compose file and in the TestContainer implementation would be more efficient than an additional command
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Testcontainer doesn’t have this problem.
Docker compose uses sleep at microservices.
A liveliness in entrypoint is nice but can be trick.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I remember that I made some liveliness probes for some jh services in one of my previous project, let me check
Please squash when merging. |
Fixes daily-build regressions related to npm scripts migration.
Please make sure the below checklist is followed for Pull Requests.
When you are still working on the PR, consider converting it to Draft (below reviewers) and adding
skip-ci
label, you can still see CI build result at your branch.