Excessive identical job parallelism in workflow about redeye

[sang2925]

Sorry about this. I will reduce the amount of runners that the cypress tests are using.

[jsf9k]

Sorry about this. I will reduce the amount of runners that the cypress tests are using.

Please don't forget to specify the purpose of running multiple, identical copies of the same job. (The value of containers from the matrix strategy is not used as far as I can tell, which is why I am saying that all the jobs are identical.)

[sang2925]

Since RedEye is using the open source version of Cypress Cloud, we can take advantage of parallelization, allowing us to run all our integration and e2e tests, both red team and blue team versions in parallel across the VMs, resulting in faster, quicker builds.
https://docs.cypress.io/guides/guides/parallelization#Overview
https://docs.cypress.io/guides/continuous-integration/github-actions#Parallelization

Although the jobs may look identical, different tests are ran within the jobs.
For example:
https://github.com/cisagov/RedEye/actions/runs/3472932203/jobs/5804454782
vs
https://github.com/cisagov/RedEye/actions/runs/3472932203/jobs/5804455116

[mcdonnnj]

This information about Cypress Cloud should be documented in the workflow. However there are only 20 slots available for GitHub Actions for the org so this workflow will completely starve the entire org of capacity until it has finished.

[GoldingAustin]

Is the entire org on the free plan with a 20 concurrent job limit? That would be excellent information to have so we can plan our action workflows around it.

[mcdonnnj]

@GoldingAustin Yes. This org is a free org with 20 runners in the pool.

[GoldingAustin]

Closing this for now, we've reduced the test actions to a single runner each #48