Skip to content

Commit

Permalink
docs: add a note about how our build reports are persisted
Browse files Browse the repository at this point in the history
  • Loading branch information
sherifnada authored Aug 2, 2022
1 parent 0ba4615 commit ff32bea
Showing 1 changed file with 6 additions and 0 deletions.
6 changes: 6 additions & 0 deletions airbyte-integrations/builds-readme.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,6 @@
# How is the builds page generated?
[This github action](https://github.com/airbytehq/airbyte/blob/master/.github/workflows/connector_integration_tests.yml) runs once a day.
It triggers builds for all connectors. The result of this build is persisted on an S3 bucket in our AWS dev environment.
Ask for access rights from the Airbyte team if you need it to access the environment. This S3 bucket is hooked up to a CDN, AWS CloudFront.
Then, [this Github action](https://github.com/airbytehq/airbyte/blob/master/.github/workflows/build-report.yml) reads from Cloudfront to send a daily
Slack message informing us of the build status of any connectors in need of attention.

0 comments on commit ff32bea

Please sign in to comment.