You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As a Galasa contributor, I want to see as much output from the Maven builds and be able to access the log and JUnit HTML report, so that I can diagnose and debug any build issues that might occur.
Workflows with Maven steps:
wrapping
maven
obr
isolated
integratedtests
simplatform
Tasks (complete for all Gradle-based workflows)
Add the -X flag to the Maven commands to enable debug level logging so users can see the exact cause of any failures
Export the Maven text log and use the upload-artefact action to upload it to the workflow so the actions user can see if anything went wrong
(If available as unsure how many of the Maven-based repos have unit tests) Export the HTML report produced for any JUnit tests and use the upload-artefact action to upload to the workflow also
Upgrade the version of Java used to 17 from 11 in the setup-java step
The text was updated successfully, but these errors were encountered:
Story
As a Galasa contributor, I want to see as much output from the Maven builds and be able to access the log and JUnit HTML report, so that I can diagnose and debug any build issues that might occur.
Workflows with Maven steps:
Tasks (complete for all Gradle-based workflows)
-X
flag to the Maven commands to enable debug level logging so users can see the exact cause of any failuresThe text was updated successfully, but these errors were encountered: