Reusable Workflows, Jobs outputs #26813
-
I’m trying to implement reusable workflow as described here: Reusing workflows - GitHub Docs on the workflow I have following jobs (simplified):
It seems like I understand that the docs stands for some limitations:
Not sure if this is a case given I’m trying to access |
Beta Was this translation helpful? Give feedback.
Replies: 5 comments
-
Is |
Beta Was this translation helpful? Give feedback.
-
No, it’s not. As you can also see that the |
Beta Was this translation helpful? Give feedback.
-
I also tried to use job outputs, indeed needs.*.outputs are empty in myjobb. The hardcoded output myin is not a secret so this must be a bug of the github actions beta. Here my public workflow run, which prints an empty needs context in myjobb. While running it with my own action service implementation locally the same workflow has the expected outputs in the needs context. I think that mforutan’s experience is about normal workflows, not about reusable workflows. Reusable workflows are documented since last Tuesday. |
Beta Was this translation helpful? Give feedback.
-
Fixed as of Today, I can confirm job outputs are now printed to the log
Update main.yml
It’s not that github wouldn’t apply changes to the actions-service at any point of time, like between our posts |
Beta Was this translation helpful? Give feedback.
-
Awesome, works for me too! |
Beta Was this translation helpful? Give feedback.
Fixed as of Today, I can confirm job outputs are now printed to the log
Update main.yml
It’s not that github wouldn’t apply changes to the actions-service at any point of time, like between our posts