Start "services" in a job that has a reusable workflow #58243
Replies: 2 comments 1 reply
-
|
I bumped to this problem as well. Would really be great if such a As a workaround we have to rework all our tests to use Testcontainers. Thanks |
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.
Uh oh!
There was an error while loading. Please reload this page.
-
Select Topic Area
Question
Body
Since this is not solved here: actions/runner#822
I'm in need of finding workarounds. The issue is many projects will use a reusable workflow, but each project has its own needs for service containers, and absolutely none of them need all services at once, which would happen if I just keep adding services in my reusable workflow's job.
The services are required for integration tests in my repos.
As an example's sake, maybe this can be easier to achieve:
Let's say I have projects that need distinct services, how can I achieve this without starting up all of them inside my reusable workflow ?
Beta Was this translation helpful? Give feedback.
All reactions