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

Fix test reports archives not generated on maven failure #29348

Closed
spbolton opened this issue Jul 24, 2024 · 0 comments · Fixed by #29349
Closed

Fix test reports archives not generated on maven failure #29348

spbolton opened this issue Jul 24, 2024 · 0 comments · Fixed by #29349

Comments

@spbolton
Copy link
Contributor

We seem to have an error in the pipeline that is causing test failures not to get generated. Essentially if the maven step fails it is not continuing in the composite action to upload the build-reports-* and build-reports-test-* archive for that step. We need to change the logic in the maven-job action to upload regardless

The build-reports-* is working it is just build-reports-test-*. it is not enough to test in the if for the inputs flag we need to explicitly allow it to run on failure with “if: always() && ${{ inputs.generates-test-results == ‘true’ }}”

  • id: generate-build-reports-artifact
    name: Generate Build Reports Artifact
    uses: actions/upload-artifact@v4
    if: always()
    with:
    name: “build-reports-${{ inputs.stage-name }}”
    path: |
    target/build-report.json
    LICENSE
    retention-days: 2
    • id: create-test-reports-artifact
      name: Create Test Reports Artifact
      uses: actions/upload-artifact@v4
      if: ${{ inputs.generates-test-results == ‘true’ }}
      with:
      name: “build-reports-test-${{ inputs.stage-name }}”
      path: |
      **/target/jacoco-report/.exec
      **/target/
      -reports/TEST-*.xml
@spbolton spbolton moved this to Current Sprint Backlog in dotCMS - Product Planning Jul 24, 2024
@spbolton spbolton moved this from Current Sprint Backlog to In Progress in dotCMS - Product Planning Jul 24, 2024
@spbolton spbolton self-assigned this Jul 24, 2024
@spbolton spbolton linked a pull request Jul 24, 2024 that will close this issue
3 tasks
github-merge-queue bot pushed a commit that referenced this issue Jul 25, 2024
#29349)

### Proposed Changes
* Force test archives to upload even when maven fails

To test
Will Test to success in PR, then will force a postman failure to force
generation of the archive and report, then fix the failure before
merging.

### Checklist
- [ ] Tests
- [ ] Translations
- [ ] Security Implications Contemplated (add notes if applicable)

### Additional Info
Related to #29348 (Fix test reports archives not generated on maven f).


### Screenshots
Original             |  Updated
:-------------------------:|:-------------------------:
** original screenshot **  |  ** updated screenshot **
github-merge-queue bot pushed a commit that referenced this issue Jul 25, 2024
#29349)

### Proposed Changes
* Force test archives to upload even when maven fails

To test
Will Test to success in PR, then will force a postman failure to force
generation of the archive and report, then fix the failure before
merging.

### Checklist
- [ ] Tests
- [ ] Translations
- [ ] Security Implications Contemplated (add notes if applicable)

### Additional Info
Related to #29348 (Fix test reports archives not generated on maven f).


### Screenshots
Original             |  Updated
:-------------------------:|:-------------------------:
** original screenshot **  |  ** updated screenshot **
@github-project-automation github-project-automation bot moved this from In Progress to Internal QA in dotCMS - Product Planning Jul 25, 2024
@nollymar nollymar moved this from Internal QA to Done in dotCMS - Product Planning Jul 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

2 participants