Replies: 3 comments
-
For the moment will go on testing the default GitHub
|
Beta Was this translation helpful? Give feedback.
-
@heldrida can you factor out this into a single separate job and use 'needs' to order your matrix job after it? |
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.
-
Select Topic Area
Question
Body
Hi,
Consider a strategy matrix that utilises a hypothetical workflow named "common-action.yml". Let's say that "common-action.yml" has a step which runs a computation that generates several artifacts across a well-defined project structure, as follows:
Each of the presented libs above might depend on each other's "computed-output", so the "computed-output" has to exist in each of the strategy matrix items or iterations. Here, we can determine that the "computed-output" should not have need to be executed for each of the strategy matrix items. A single "compute" to generate all "computed-outputs" should be sufficient, as it'd effectively generate the same output.
Thus, the question is how to best handle this to cache and reutilize the desired cached resource, e.g.,
project/**/computed-output/**/*
?Here's some pseudo workflows to illustrate the use-case:
The parent workflow
The common-action
Beta Was this translation helpful? Give feedback.
All reactions