testing a simple CI config first

[CapoMK25]

Brief description

This is just a test for GitHub Actions in the future, might fail completely on the first run and might not even work together with Jenkins, since Jenkins is still active.

Change list

• Added two workflows for the actions runners, thus the 2 added files. ci.yml and coverage.yml

[CapoMK25]

Too strict, has to rerun the classic Mongo test isolation bugs instead of failing the run completely. Adjusting.

[CapoMK25]

--runinband makes the CI loop forever on Actions, needs to be addressed in the coming days by me.

[hoan301298]

I think the current setup makes sense. Approved! Well done.

In the dedicated coverage.yml workflow, using if-no-files-found: error also makes sense since generating coverage is the primary goal there.

I added comments, some of them were from AI suggestions. Feel free to discuss and if you think they're no need for this ci workflows, ignore them 👍

[hoan301298]

I think now we are using the lower version of node 20/22. It might be a problem in future. Just choose a safer one. Please check other usage as well. 😄

[tickBit]

I'm currently using Node v25.9.0

[hoan301298]

guarantee coverage exists

run: | 
    npm run test -- \ 
    --coverage \ 
    --json \ 
    --outputFile=test-results.json

[hoan301298]

Prevents old coverage runs from continuing after new commits are pushed

concurrency:
  group: coverage-${{ github.ref }}
  cancel-in-progress: true

[hoan301298]

The dedicated coverage workflow exists specifically to generate coverage.

If the coverage/ folder is missing there, something is wrong:

tests didn’t run correctly
coverage config broke
Jest stopped generating reports

So failing the workflow is useful:

if-no-files-found: error

because coverage generation is the primary goal of that workflow.