feat: Add support for filtering Jobs by an array of scopes

[X-Guardian]

Summary

Add support for the scope parameter to accept both string and array of strings in Jobs API methods, aligning with the GitLab API.

Changes

Updated Methods

• Jobs.all() - Updated scope parameter to accept JobScope | JobScope[]
• Jobs.allPipelineBridges() - Updated scope parameter to accept JobScope | JobScope[]

Reference

• GitLab API Documentation: https://docs.gitlab.com/api/jobs/#list-project-jobs

[X-Guardian]

Hi @jdalrymple, I'm getting intermittent test failures i.e.: https://circleci.com/gh/jdalrymple/gitbeaker/1719

 FAIL  test/unit/resources/Search.ts
  ● Test suite failed to run

    A jest worker process (pid=341) was terminated by another process: signal=SIGKILL, exitCode=null. Operating system logs may contain more information on why this occurred.

      at ChildProcessWorker._onExit (../../node_modules/.pnpm/jest-worker@30.2.0/node_modules/jest-worker/build/index.js:968:23)

 FAIL  test/unit/resources/Deployments.ts
  ● Test suite failed to run

    A jest worker process (pid=385) was terminated by another process: signal=SIGKILL, exitCode=null. Operating system logs may contain more information on why this occurred.

But I think the change is good, and I've tested it locally against gitlab.com

[jdalrymple]

Hi @jdalrymple, I'm getting intermittent test failures i.e.: https://circleci.com/gh/jdalrymple/gitbeaker/1719

 FAIL  test/unit/resources/Search.ts
  ● Test suite failed to run

    A jest worker process (pid=341) was terminated by another process: signal=SIGKILL, exitCode=null. Operating system logs may contain more information on why this occurred.

      at ChildProcessWorker._onExit (../../node_modules/.pnpm/jest-worker@30.2.0/node_modules/jest-worker/build/index.js:968:23)

 FAIL  test/unit/resources/Deployments.ts
  ● Test suite failed to run

    A jest worker process (pid=385) was terminated by another process: signal=SIGKILL, exitCode=null. Operating system logs may contain more information on why this occurred.

But I think the change is good, and I've tested it locally against gitlab.com

Ive seen these as well. I've tried to figure out where its coming from but it seems inconsistent. I've been looking for solutions to hopefully get around this behaviour.

[X-Guardian]

Ive seen these as well. I've tried to figure out where its coming from but it seems inconsistent. I've been looking for solutions to hopefully get around this behaviour.

I expect the container is running out of memory. Have you tried bumping the CircleCI node-executor resource class to medium+ (6GB) or large (8GB)? They look like they are available on the free tier.

[jdalrymple]

Ill give it a look! Not sure why jest is needing 8Gbs though :/ hahaha, i might shard them to see if that improves things