Replies: 2 comments
-
|
I have the same question. What happens if the calling workflow runs on ubuntu-latest and the reusable workflow runs on windows-latest? Does it inherit the OS from the caller, or does each job run on the OS defined in its own file? |
Beta Was this translation helpful? Give feedback.
-
|
🕒 Discussion Activity Reminder 🕒 This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions: 1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as 2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own. 3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution. Note: This dormant notification will only apply to Discussions with the Thank you for helping bring this Discussion to a resolution! 💬 |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Why are you starting this discussion?
Question
What GitHub Actions topic or product is this about?
Workflow Configuration
Discussion Details
I cannot find any documentation that explains how exactly
runs-onworks when the main workflow and reusable workflow have different configuration for it. Ex., one iswindows-latestand another isubuntu-latest.Will it fail to run? Will it use the OS from the caller? Will it run with different OS, and how it shares the filesystem in this case?
In my case, I'm wondering if I can do a Windows specific step (like producing a windows
.exe) and then continue working with the file (ex. sign, upload somewhere, other postprocessing) using Ubuntu specific tools.Beta Was this translation helpful? Give feedback.
All reactions