Pairwise now relies on 3 external APIs which are used in the workspace challenges:
These are all deployed using Google Cloud Build, and currently do not forward any notifications if builds fail. As a result the builds might fail silently, which is not ideal. However these services are not updated that frequently.
In addition, the Pairwise website (https://github.com/pairwise-tech/website) now deploys directly using the Netlify GitHub integration, and also does not forward build status notifications to Slack.
Ideally all of these other deployments would have Slack notifications to alert us if they fail from time to time.
Pairwise now relies on 3 external APIs which are used in the workspace challenges:
These are all deployed using Google Cloud Build, and currently do not forward any notifications if builds fail. As a result the builds might fail silently, which is not ideal. However these services are not updated that frequently.
In addition, the Pairwise website (https://github.com/pairwise-tech/website) now deploys directly using the Netlify GitHub integration, and also does not forward build status notifications to Slack.
Ideally all of these other deployments would have Slack notifications to alert us if they fail from time to time.