[
https://issues.apache.org/jira/browse/MNG-8685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tamas Cservenak updated MNG-8685:
---------------------------------
Summary: Support CI system, some allow "debug" jobs, propagate that mode to
Maven (was: Propagate GitHub Actions debug mode to Maven)
> Support CI system, some allow "debug" jobs, propagate that mode to Maven
> ------------------------------------------------------------------------
>
> Key: MNG-8685
> URL: https://issues.apache.org/jira/browse/MNG-8685
> Project: Maven
> Issue Type: Improvement
> Components: Command Line
> Reporter: Tamas Cservenak
> Assignee: Tamas Cservenak
> Priority: Major
> Fix For: 4.0.0-rc-4
>
>
> When in debug mode, GitHub Actions adds the `RUNNER_DEBUG` environment
> variable, cf
> https://github.com/actions/toolkit/blob/1b1e81526b802d1d641911393281c2fb45ed5f11/packages/core/src/core.ts#L258-L260.
> It would be a great improvement for scoped troubleshooting to propagate this
> option to Maven. The use case is the following:
> * A GitHub Actions workflow fails on a call to `mvn`
> * We relaunch the failed jobs with the [debug mode
> enabled](https://docs.github.com/en/actions/managing-workflow-runs-and-deployments/managing-workflow-runs/re-running-workflows-and-jobs#about-re-running-workflows-and-jobs)
> * Maven also displays its debug logs this time 🎉
> It felt like such a minor change could avoid a new Jira entry, however I
> still can create one if you think it's best.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
