Concurrency and Reusable Workflows with multi-repositories #88761
Replies: 2 comments
-
🕒 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.
-
have you found a solution to this? |
Beta Was this translation helpful? Give feedback.
-
Select Topic Area
Question
Body
I have two repos, one for UI and other for Tests, I can't have two tests running at the same time so I added concurrency to the Tests repo, if that workflow is triggered twice it guarantees that it will not run at the same time. It worked.
Now I need to make the UI repo call the Tests workflow so I used the
workflow_call
trigger to accomplish this, but it seems that the concurrency is not working across repos.I mean, if I trigger the Tests workflow on UI repo and Test repo at the same time, both will run together.
Is there a way that I can force concurrency between the repos?
Like if the UI repo is currently running the Test workflow, if I trigger the Test workflow on the Test repo it will keep pending and run only after the UI repo finishes the job.
Thank you for the help.
UI workflow:
Tests workflow:
Beta Was this translation helpful? Give feedback.
All reactions