By default command execution should be set to "always" | Feature Requests

By default command execution should be set to "always"

Mayank Shukla

Currently when we define any command then it only gets executed when the job passes. However, there are mostly chances where we want our command to be executed always no matter the job passed or failed. Can we have by default command execution set to "always"?

June 12, 2025

Jaxonn

it is possible to configure command execution to always run, regardless of the job's outcome. You can typically achieve this by using a specific setting or directive in your job configuration (like always(slope game) in CI/CD pipelines) that ensures the command runs after the job completes, whether it passes or fails.

Gordon Bolton

Totally agree with this! It would make workflows much more intuitive, especially for cleanup or notification steps. Having "always" as the default would save time and reduce potential errors.

snow rider