-
Notifications
You must be signed in to change notification settings - Fork 4.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Connector Ops CI: introduce QA engine #21709
Conversation
Airbyte Code Coverage
|
816197d
to
8b0b886
Compare
@@ -0,0 +1,30 @@ | |||
name: Run QA Engine |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I could not test this workflow as it needs to be on the main branch to be manually triggered.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This might be helpful for you: https://github.com/airbytehq/github-workflow-test-repo-base (see readme, topher directed me toward it)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
seems like a good start!
with: | ||
service_account_key: ${{ secrets.PROD_SPEC_CACHE_SA_KEY }} | ||
export_default_credentials: true |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this a new secret?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nope, it's the one used by the deploy-oss-catalog.yml workflow, we use it to write to GCS.
What
Closes #21711
I want to bootstrap the QA engine with this PR.
It introduces a new GitHub action workflow, which is triggered daily and write the QA engine results to GCS.
It's not currently computing anything at the moment.
We're just defining:
How
qa-engine
package in theci_connectors_ops
packageinputs
,models
,main
modulessetup.py