Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

always() fails to run if needs jobs are skipped #3664

Open
dv01d opened this issue Jan 17, 2025 · 0 comments
Open

always() fails to run if needs jobs are skipped #3664

dv01d opened this issue Jan 17, 2025 · 0 comments
Labels
bug Something isn't working

Comments

@dv01d
Copy link

dv01d commented Jan 17, 2025

Describe the bug
It is impossible to always run a job

To Reproduce
Steps to reproduce the behavior:

  1. Add jobs to workflow
  2. Create a last job that needs all jobs so it runs last
  3. use always() as a condition in if
  4. If any needs jobs are skipped always() job is also skipped

Expected behavior
I would expect always() to return true and job is ran

Runner Version and Platform

latest

OS of the machine running the runner? OSX/Windows/Linux/...
Linux

What's not working?

When is always() not always? When is true not true? I have tried using the following if condition
if: ${{ true || always() || failure() || success() || cancelled() || needs.*.result == 'skipped' }}

Runner and Worker's Diagnostic Logs

Reasons for skip are never logged, nor are their logs for decision.

@dv01d dv01d added the bug Something isn't working label Jan 17, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant