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
This works well if it's in a workflow, even if a reusable one. However, it doesn't work for me if the same above code is in a composite action, that is being executed when the cancel comes. So, e.g. canceling this workflow yields the always()-using step running. However, the same step in this composite action in the same run just doesn't execute:
ActionsBuild, test, and automate your deployment pipeline with world-class CI/CDProduct Feedback
1 participant
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
When you'd like to run a job step always, even if the workflow was canceled, you can use the
always()
function:This works well if it's in a workflow, even if a reusable one. However, it doesn't work for me if the same above code is in a composite action, that is being executed when the cancel comes. So, e.g. canceling this workflow yields the
always()
-using step running. However, the same step in this composite action in the same run just doesn't execute:Is this a limitation of composite actions?
Beta Was this translation helpful? Give feedback.
All reactions