[
https://issues.apache.org/jira/browse/YUNIKORN-2893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yu-Lin Chen updated YUNIKORN-2893:
----------------------------------
Description:
Currently, when a newer commit is pushed to the same PR, the previous build is
not canceled. To save cost, we should apply the "cancel-in-progress" to
automatically cancel previous build.
REF:
[https://docs.github.com/en/enterprise-cloud@latest/actions/writing-workflows/choosing-what-your-workflow-does/control-the-concurrency-of-workflows-and-jobs#using-concurrency-in-different-scenarios]
was:
Currently, when a newer commit is pushed to the same PR, the previous build is
not canceled. To save cost, we should apply the "cancel-in-progress" to
automatically cacncel previous build.
REF:
[https://docs.github.com/en/enterprise-cloud@latest/actions/writing-workflows/choosing-what-your-workflow-does/control-the-concurrency-of-workflows-and-jobs#using-concurrency-in-different-scenarios]
> Apply "cancel-in-progress" feature for each PR in Github Action
> ---------------------------------------------------------------
>
> Key: YUNIKORN-2893
> URL: https://issues.apache.org/jira/browse/YUNIKORN-2893
> Project: Apache YuniKorn
> Issue Type: Improvement
> Components: build
> Reporter: Yu-Lin Chen
> Priority: Major
>
> Currently, when a newer commit is pushed to the same PR, the previous build
> is not canceled. To save cost, we should apply the "cancel-in-progress" to
> automatically cancel previous build.
> REF:
> [https://docs.github.com/en/enterprise-cloud@latest/actions/writing-workflows/choosing-what-your-workflow-does/control-the-concurrency-of-workflows-and-jobs#using-concurrency-in-different-scenarios]
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
