-
I had a test that hung and I got a notification that it was killed after 6 hours. This seems wasteful. Is there a way to configure a time limit for the workflows? For me, after 20 minutes I’m really not expecting anything to still be active. |
Beta Was this translation helpful? Give feedback.
Replies: 4 comments
-
Here you go https://help.github.com/en/articles/workflow-syntax-for-github-actions#jobsjob_idstepstimeout-minutes |
Beta Was this translation helpful? Give feedback.
-
You can add timeout-minutes: 20 to your job: For example: See also: |
Beta Was this translation helpful? Give feedback.
-
If I have many repos and each repo has many actions, it will be very difficult to apply this setting manually on every action. Is there an org level setting, so that the Org Admin can set it and it will get applied for each action in each repo belonging to that org? That way, the Org Admin can control it for all the repos from a central location. |
Beta Was this translation helpful? Give feedback.
-
Indeed, it would be really great to have control about the Github Actions timeouts at the organization level, while still being able to override them on per job basis. Or maybe a general hard limit, for the whole organization and/or repository. The number of minutes consumed by a job affects billing directly, so the organization has to be able to enforce some limits there. Currently, a single mistake in a job, causing it to hang for example, can cause the exhaustion of all the available minutes. |
Beta Was this translation helpful? Give feedback.
You can add timeout-minutes: 20 to your job:
For example:
See also: