Finish the CI/CD

[akauppi]

So that:

• [ ] pushing (or merging to) master
  • when relevant files in packages/backend have changed,
    • [ ] runs backend tests (if they fail, the push/merge fails)
    • [ ] deploys to Firebase
• [ ] creating a PR targeting master
  • when relevant files in packages/backend have changed,
    • [ ] runs backend tests (if they fail, the PR is marked as "tests fail")
• [ ] pushing (or merging to) master
  • when relevant files in packages/app have changed,
    • [ ] runs app tests (Cypress) (if they fail, the push/merge fails)
    • [ ] builds a deployable image (if that fails, the push/merge fails)
    • [ ] deploys to Firebase
• [ ] creating a PR targeting master
  • when relevant files in packages/app have changed,
    • [ ] runs app tests (Cypress) (if they fail, the PR is marked as "tests fail")
• [ ] pushing (or merging to) master
  • when relevant files in packages/app-deploy-ops have changed,
    • [ ] builds a deployable image (if that fails, the push/merge fails)
    • [ ] deploys to Firebase
• [ ] creating a PR targeting master
  • when relevant files in packages/backend have changed,
    • [ ] builds a deployable image (if that fails, the push/merge fails)

Latest error:

$ cd builds
$ $ gcloud builds submit ..
...
Step #4: i  functions: updating Node.js 14 (Beta) function userInfoShadow_2(europe-west6)...
Step #4: ⚠  functions: failed to update function userInfoShadow_2
Step #4: HTTP Error: 403, Missing necessary permission iam.serviceAccounts.actAs for $MEMBER on the service account groundlevel-160221@appspot.gserviceaccount.com.
Step #4: Grant the role 'roles/iam.serviceAccountUser' to $MEMBER on the service account groundlevel-160221@appspot.gserviceaccount.com.
Step #4: You can do that by running 'gcloud iam service-accounts add-iam-policy-binding groundlevel-160221@appspot.gserviceaccount.com --member=$MEMBER --role=roles/iam.serviceAccountUser'.
Step #4: In case the member is a service account please use the prefix 'serviceAccount:' instead of 'user:'.
Step #4: If this is a cross-project service account usage. Ask a project owner to grant you the iam.serviceAccountUser role on the service account and/or set the iam.disableCrossProjectServiceAccountUsage org policy to NOT ENFORCED on the service account project. Please visit https://cloud.google.com/functions/docs/troubleshooting for in-depth troubleshooting documentation.

[akauppi]

Triggers can be made from the CLI: https://cloud.google.com/build/docs/automating-builds/create-manage-triggers

[akauppi]

Changing the spec in the way that:

• PRs towards master and staging (to be done) are handled; show the status in GitHub
• Push to master and staging (later) will run tests and deploy the change parts (backend, app, or both) if those tests pass

We cannot prevent direct pushes to a branch. Cloud Build / GitHub integration doesn't allow that.

Related: #50

[akauppi]

• [ ] Cypress support (while having Firebase Emulation support) requires its own image to be done

  • likely needs to be based on cypress/base since there's not a set that would work on Alpine (is there??)

• track https://github.com/cypress-io/cypress-docker-images/issues/110

[akauppi]

CI now done enough (see ci/README).

• Backend PRs fully done
• App PRs require the Cypress image: cont'd in #50
• Deployment can remain manual, for now.