Christian Nicolai

> It seems that the test was is working by observing [here](https://github.com/camunda/camunda/actions/runs/10614567736/job/29442431525?pr=21685). The cache operation was run creating one with the key `github-hosted-macOS-mvn-shared-b8f0f396e1172a55c103b6acfb8bc8217f2fef46e76fe9156890ec1d0b4e4745 ` and restoring from the same key...

> To test that effectively you probably have to change the cache key temporarily to something unique so no cache restore is possible -> means that cache creation will be...

> [here](https://github.com/camunda/camunda/actions/runs/10666794638/job/29563145662?pr=21685#step:15:5) we can see that the cache was created successfully in the post run step like you suggested. > > The test commit had the condition inverted to allow...

Subtask https://github.com/camunda/team-infrastructure/issues/679

Closing since sub-task was closed. Follow-up work will be part of https://github.com/camunda/team-infrastructure/issues/736

The 2nd contribution in June 2024 that I'm aware of and is blocked by this: * https://github.com/camunda/camunda/pull/18885

> I followed the suggested workaround, but there are still two (unrelated) CI jobs failing: > * [feat(clients/go): jobWorker can set tenantIds to activate jobs #20075](https://github.com/camunda/camunda/pull/20075) > @cmur2 Is there...

> My PR #24327 has been closed without merging because of this issue here.... > > It's kind of strange that my contribution is now blocked by this issue here...

FYI: It is now technically possible again to merge PRs from forks since all [required status checks](https://github.com/camunda/camunda/wiki/CI-&-Automation#faq-1) can become green 💚 ([demo](https://github.com/camunda/camunda/pull/25435#issuecomment-2507584182)) Workarounds are no longer necessary but keep in...

This is bothering me as well, is it possible to release an update?