-
-
Notifications
You must be signed in to change notification settings - Fork 4k
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
Create GitHub Actions to improve CI maintainability. #15129
Comments
Agree with you @mshima When I coded this part, in the past, I tried to put everything inside shell scripts:
Today, we have a lot of logic directly inside yml files. I think we should move logic into shell scripts. The yml files should only contain configuration (ngx, react, vue, database etc) |
Still thinking if we could use gradle as our build runner, so we can benefit from the up-2-date checks (in case we define correct inputs for each task), but of course it would be tight to the main repository only. |
I don't think we will have many benefits from up-2-date checks. When pushing to main branch is important to run the tests due to transitive dependencies. |
@mshima : approved |
Overview of the feature request
Implement custom actions to be shared between jhipster repositories.
Motivation for or Use Case
JHipster CI consists in:
Currently, to change some build process, each workflow must be updated manually to reflect the changes.
JHipster-BOM repository CI is failing, but should be identical to the generator-jhipster CI.
Related issues or PR
The text was updated successfully, but these errors were encountered: