Skip to content
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

Merged
merged 9 commits into from
Feb 28, 2024

Conversation

murdos
Copy link
Contributor

@murdos murdos commented Feb 22, 2024

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}'

Copy link

codecov bot commented Feb 22, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 100.00%. Comparing base (ea64095) to head (29998ec).

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.
📢 Have feedback on the report? Share it here.

Comment on lines -323 to +326
./generate.sh ${{ matrix.app }} ${{ matrix.spring-config-format }}
./generate.sh ${{ matrix.app }} ${{ matrix.java-build-tool }} ${{ matrix.spring-config-format }}
Copy link
Contributor

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

Copy link
Contributor Author

@murdos murdos Feb 23, 2024

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.

Copy link
Contributor

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 👍

This was referenced Feb 27, 2024
…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}'
@murdos murdos merged commit 8b35fd2 into jhipster:main Feb 28, 2024
37 checks passed
@murdos murdos deleted the ci/java-build-tool-matrix branch February 28, 2024 11:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants