-
-
Notifications
You must be signed in to change notification settings - Fork 198
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
(ci) Introduce java-build-tool in build matrix #8986
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #8986 +/- ##
===========================================
Coverage 100.00% 100.00%
Complexity 2899 2899
===========================================
Files 733 733
Lines 12514 12514
Branches 254 254
===========================================
Hits 12514 12514 ☔ View full report in Codecov by Sentry. |
./generate.sh ${{ matrix.app }} ${{ matrix.spring-config-format }} | ||
./generate.sh ${{ matrix.app }} ${{ matrix.java-build-tool }} ${{ matrix.spring-config-format }} |
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.
Should this change need to be done at the following step too?
- name: 'Generation: generate ${{ matrix.app }} from main branch'
if: github.event_name == 'pull_request'
working-directory: ./main-branch/tests-ci/
run: |
./start.sh 7471
./generate.sh ${{ matrix.app }} ${{ matrix.spring-config-format }}
./stop.sh
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 thought about it, but I came to the conclusion that this change should be made once this PR is merged, because script of main branch still uses 2 input parameters.
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.
Ohh! That's true, thank you for this great improvement 👍
…tion This will help testing more easily different gradle application. And this will solve the issue of applying a feature rather than a module: since we can't apply through JHipster REST API a feature 'github-actions' that regroups either 'github-actions-maven' or 'github-actions-gradle', we can either have bash function that return the right module for the java-build-tool or use expression like 'github-actions-${java_build_tool}'
48194d5
to
29998ec
Compare
It allows better handling of build cache, and this will help testing more easily different gradle applications.
This will also solve the issue of applying a feature rather than a module: since we can't apply through JHipster REST API a feature 'github-actions' that regroups either 'github-actions-maven' or 'github-actions-gradle', we can either have bash function that return the right module for the java-build-tool or use expression like 'github-actions-${java_build_tool}'