Howdy! Can somebody tell me what is the current situation and plans regarding CI for Perforce modules? All perforce-* modules I check, and all PRs I am notified about or open for these modules have a broken CI. I am thinking that we should just merge PRs regardless of the CI results, release new versions and let users report regressions if there are some… that would still be a better situation than the current one.

There is a known issue where CI cannot run on PRs from folks outside the puppetlabs organization because of a security setting that prevents the necessary secrets from being released. It is secure, but then causes the CI issue with PRs. That might be what you are seeing here? There is an item for review with product to get this looked at, but I believe there is a workaround being used in the meantime where engineering tests the PR and merges it. Unfortunately no concrete update can be given on a timeline for fixing the issue with secrets releases, sorry about that! (And sorry for the delay in responding, holiday times mean many of us are out of office)

That might be what you are seeing here?

I don't know. I don't think I can know for sure… Maybe 🤷 Note that this blocked PR was opened by a trusted contributor, due to the annoyances caused by this bug we could merge and release a new patch release of the module without needing the tests passing, but it really is not cool from a community point of view.