[
https://issues.apache.org/jira/browse/MNG-8013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17805931#comment-17805931
]
Slawomir Jaranowski commented on MNG-8013:
------------------------------------------
We can create a artifact with logs file, some thing like:
{code}
- name: Upload artifact on failure
uses: actions/upload-artifact@v4
if: failure()
with:
name: ${{ github.run_number }}-failure-${{ matrix.os }}-${{
matrix.jdk }}-${{ matrix.distribution }}
path: .... to discover
{code}
copy from:
https://github.com/apache/maven-gh-actions-shared/blob/v3/.github/workflows/maven-verify.yml#L292-L297
> Integration testing process logs can be output Github action log
> ----------------------------------------------------------------
>
> Key: MNG-8013
> URL: https://issues.apache.org/jira/browse/MNG-8013
> Project: Maven
> Issue Type: Task
> Reporter: Zhongming Hua
> Priority: Major
>
> Related Jira: https://issues.apache.org/jira/browse/MNG-7976
> If we can show the maven build process in maven's ci log, such as
> maven-integration-testing/core-it-suit/target/test-classes/mng-6127-plugin-execution-configuration-interference/project/log.txt.
> we can more easily troubleshoot some occasional problems.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
