Add GitHub Actions CI

[bahmutov]

To show how to run Cypress e2e tests using the new GitHub Actions CI

• record to Dashboard
• run several containers in parallel

[kieranklaassen]

Would love to see GitHub actions CI implemented on the repo!

[bahmutov]

@amirrustam was working on it, seems actions are still missing proper NPM caching and also the environment variables for parallel runs are somewhat tricky

[amirrustam]

Working closely with GH team to on this that will potentially improve some of these beta-level wrinkles for everyone.

[HugoGresse]

I was smoothly able to record on dashboard with the new Github Actions
see https://github.com/HugoGresse/open-feedback/blob/master/.github/workflows/test-e2e.yml
I have not tried the parallelization though.

[csi-lk]

Also have setup a really simplistic version here

[mikecousins]

Any idea how to get an environment variable from Github Actions that we can use for --ci-build-id?

[HugoGresse]

@mikecousins you can setup env var from the Github repo settings ans use them like so:

    - name: npm install, build
      run: |
        npm install
        npm run build --token ${{ secrets.REACT_APP_API_KEY }}
      env:
        CI: true
        REACT_APP_API_KEY: ${{ secrets.E2E_FIREBASE_API_KEY }}

[mikecousins]

Yeah but we need something unique on every run like a build id, build number, etc. Closest I can see in Github is the commit sha, but then it's not re-runnable.

[jbolda]

I have got it pushing into cypress with parallel, but it doesn't seem to connect back and pass the checks to the github integration. I have set a few of the git related env vars that don't seem to fill in, but it still seems to be missing something. I have an open PR that I am working through switching from Travis CI recording to Github Actions. Below are the env vars I have set so far. COMMIT_INFO_BRANCH because it seems to return null every time, and COMMIT_INFO_REMOTE because it doesn't end with .git, which may or may not be a problem.

        COMMIT_INFO_BRANCH: ${{ github.head_ref }}
        COMMIT_INFO_REMOTE: https://github.com/${{ github.repository }}.git

[mikecousins]

What are you using for your --ci-build-id @jbolda?

[jbolda]

Basically just the commit sha because as you mentioned, don't seem to have any other choice. I thought about maybe trying to grab a timestamp, but didn't want to reinvent the wheel if a better option might be coming.

[amirrustam]

Depending on your setup, commit sha is not the really the most unique CI build id, and might lead to issues. You could generate a UUID for each run instead.

[bahmutov]

Related: cypress-io/cypress#5609

[bahmutov]

🎉 This issue has been resolved in version 1.9.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀