On Mon, Feb 28, 2022 at 8:00 PM Basil Crow <m...@basilcrow.com> wrote:
> After upgrading a dozen or so plugins to Security Scan v2, the Jenkins > Security Scan workflow on the main branch failed with: > > Called workflows cannot be queued onto self-hosted runners across > organisations/enterprises. Failed to queue this job. Labels: > 'ubuntu-latest'. > Interesting, I haven't seen this during development and that includes repos in jenkinsci. Some searching indicates you're being rate-limited: https://github.community/t/called-workflows-cannot-be-queued-onto-self-hosted-runners-across-organisations-enterprises-failed-to-queue-this-job-labels-ubuntu-latest/229355/10 (which got a GH team response, they seem to be looking into this). If you pushed out the changes to the YAML files in quick succession, that might explain it? It looks like you were particularly active around 18:10. Looks like I'll need to look into adding this to the pipeline library sooner rather than later :-) -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAMo7PtLzWF16%3DODcY%2Bds4zNWojCeceyXAGWGVRYNtQmgxZEyYQ%40mail.gmail.com.
