-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
ci: fix failing airbyte-ci-install
(related to ubuntu-latest
image no longer compatible with airbyte-ci
binaries)
#50992
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
Noting for visbility and future reference: Failure still occured when we pre-run setup-python. Suspected cause is that binary for |
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.
/format-fix
airbyte-ci-install
(related to ubuntu-latest
image no longer compatible with airbyte-ci
binaries)
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.
BAM! 💥
For anyone else who's running into this issue outside of Github Actions: We're also running into this issue in Codebuild using the |
What
Our CI workflows were using worker definitions that were based on
ubuntu-latest
, even though in the code there was no reference toubuntu-latest
in the workflow itself.The problem with this is that the definition of
ubuntu-latest
changed to now point toubuntu-22.04
. The published binary versions ofairbyte-ci
seem to be incompatible with the ubuntu we are using now. We tried rolling this back but it wasn't successful. The fix we found was to always use the Python-based installation ofairbyte-ci
- at least for now.Note:
Vercel is still failing as of now. We will need to research this, most likely. In the meanwhile, this PR will at least unblock devs to work on connectors.
Org runners definitions (requires org admin permissions):
connector-test-large
: https://github.com/organizations/airbytehq/settings/actions/github-hosted-runners/5?viewing_from_runner_group=falselinux-20.04-large
: https://github.com/organizations/airbytehq/settings/actions/github-hosted-runners/40?viewing_from_runner_group=falseCan this PR be safely reverted and rolled back?