Changing instance type of AWS self-hosted runner from from c5.2xlarge to c6a.4xlarge.
It will result in:
CPU: 8 -> 16
Sustained clock speed (GHz): 3.4 -> 3.6
RAM: 16 -> 32
cost: 0.34 USD/hr -> 0.612 USD/hr
it seems github APIs want us to use longer shas in some cases where a
7 character short sha is still entirely valid
So just set the minimum short sha length to 10
* start
* revert
* azblob
* bq
* bq denorm
* megapublish baaaabyyyy
* fix needs
* matrix connectors
* auto-bump connector version
* dont failfast and max parallel 5
* multi runno
* minor
* testing matrix agents
* name
* testing multi agents
* tmp fix
* new multi agents
* multi test
* tryy
* let's do this
* magico
* fix
* label test
* couple more connector bumps
* temp
* things
* check this
* lets gooo
* more connectors
* Delete TEMP-testing-command.yml
* auto-bump connector version
* added comment describing bash part
* running single thread
* catch sentry cli
* auto-bump connector version
* destinations
* + snowflake
* saved
* auto-bump connector version
* auto-bump connector version
* java source bumps
* auto-bump connector version
* auto-bump connector version
* auto-bump connector version
* auto-bump connector version
* auto-bump connector version
* auto-bump connector version
* auto-bump connector version
* auto-bump connector version
* auto-bump connector version
* auto-bump connector version
* auto-bump connector version
* auto-bump connector version
* auto-bump connector version
* auto-bump connector version
* auto-bump connector version
* auto-bump connector version
* auto-bump connector version
* auto-bump connector version
* auto-bump connector version
* remove twice-defined methods
* label things
* revert action
* using the new test action
* point at action
* wrong tag on action
* update pool label
* update to use new ec2-github-runner fork
* this needs to be more generic than publisher
* change publish to run on pool
* add comment about runner-pool usage
* updated publish command docs for multi & parallel connector runs
* auto-bump connector version
* auto-bump connector version
* auto-bump connector version
* unbump failed publish versions
* missed dockerfiles
* remove failed docs
* mssql fix
* overhauled the git comment output
* bumping a test connector that should work
* slight order switcheroo
* output connectors properly in first message
* auto-bump connector version
Co-authored-by: Octavia Squidington III <octavia-squidington-iii@users.noreply.github.com>
* Rename docker secrets and parameterize docker user
* Apply suggestions from code review
Co-authored-by: Pedro S. Lopez <pedroslopez@me.com>
Co-authored-by: Pedro S. Lopez <pedroslopez@me.com>
* added multiarch image publishing/modified dockerfiles
* added new ami
* changed version to test
* rollback version
* check version test
* env vars temp fix
* apt-utils error fix
* disabled failed test
* remove excluded tests
* Excluded :airbyte-db:lib:test
* Excluded :airbyte-db:lib:test
* static jdk version for test
* ok test
* ok test
* ok test
* test vars
* quemu issue fix
* Returned version vars
* Scripts update
* Version vars change
* Comment fix
* Added comments, minor changes and comments in dockerfiles
* Uncomment line to push images
* Dockerfile to 3.9
* Python version
* More python updates
* 3.9 on GitHub actions and lint updates
* Test out 3.9.11 on GitHub actions
* install python with an action
* formatting: newline
* Also has python code
* only check first level for changed modules
Previous example (source-google-search-console/credentials)
* Test failure: there is no logger.trace
* Revert "Revert "Build OSS branch for deploying to Cloud env (#11474)""
This reverts commit 55e3c1e051.
* add action to get dev branch tag to OSS project instead of doing it in cloud
* remove dev branch version action, going to do this in cloud afterall
* add VERSION buildArg to Dockerfiles, default to current airbyte version but overwritable
* use VERSION env var consistently as Dockerfile buildArg, jar version, and tag
pass version and image_tag into docker build task function
* add github action for building and pushing an OSS branch for Cloud to consume
* allow AirbyteVersion to validate versions containing 'oss-branch' prefix
* change oss-branch prefix to dev for branch-based versions
* better action name
* add docker-compose-cloud.build.yaml to define minimum set of cloud images that are pushed by oss branch action
* update local dev docs to describe optional usage of VERSION env var
* make branch_version_tag input optional, if not provided, generates dev-<commit_hash>
* fix typo
* fix missed merge conflict
* update docker docs
* update integrationRunner isDev check
* Use shell hacks to find valid PAT
if rate limit exceeded try another key
* Use tim's version of the ec2 runner
this is a weird solution with weird limitations. should address the short term pain (march 2022)
* Adds tim's ocotocat rate limiter
* Change all the actions to our homebrew ec2 fork
* Compiles the dist in npm
* Update action to v15.0.1
* Update to v15.0.2
* Update to v15.0.3
* Update to v15.0.4
Co-authored-by: Tim Roes <tim@airbyte.io>
Due to actions/runner#1605, all our builds are failing.
This changes pins us to machulav/ec2-github-runner#88 until a more stable solution is available.
Either the upstream action merges this in and we bump our version, or Github reverts their breaking change.
