* Revert "Revert "Add dependencies to docker-compose (#19257)" (#19306)"
This reverts commit b16f28fd4d.
* Bump docker-compose version
* test
* Revert "test"
This reverts commit c3b28c9ec3.
* Bump docker compose version to 3.8
* test
* test
* Use a newer docker for platform build
* test
* Use docker compose v2
* Update docker for frontend e2e
* Use docker compose v2 for e2e tests
* Update tools to use docker compose v2
* Update more docker compose references to v2
* Update docker compose usage in docs
* Update deploying airbyte docs
* Fix permission
* Case insensistive check
* Add extra mention for docker compose in upgrading airbyte
* Improve upgrade docker note
* wip
* wip
* e2e tests for connector builder server
* rename function
* clean up
* clean up a bit more
* fix path
* fix and add documentation
* more documentation
* stabilze
* review comments
It's difficult today to parse all the logs from tests. Engineers waste time scrolling through the log outputs and looking for the relevant stack trace.
This PR adds an action to generate a JUnit report so devs can understand test results at a glance. This generates 3 reports for each of the main build jobs when the build completes. We leave the frontend build out since this is aggregated by cypress.
See https://github.com/airbytehq/airbyte/pull/15271/checks?check_run_id=7683783016 for an example of how this works.
Use the https://github.com/dorny/test-reporter action and configure this to look at the Jacoco test report output for top level and second level builds. Note that most of the parameters into the action don't work.
Comment out the trap commands to output logs. Though this can be useful for debugging, there is little practical use in the day-to-day, and results in extremely noisy logs.
* Record e2e tests to cypress dashboard
* Make env variable accessible in script
* Improve e2e_test script
* Properly wait for server to be ready
* Isolate test suites better
* More test isolation
* Revert baseUrl for development
* Implement db config persistence
* Fix database readiness check
* Reduce logging noise
* Setup config database in config persistence factory
* Update documentation
* Load seed from yaml files
* Refactor config persistence factory
* Add one more test to mimic migration
* Remove unnecessary changes
* Run code formatter
* Update placeholder env values
* Set default config database parameters in docker compose
Co-authored-by: Christophe Duong <christophe.duong@gmail.com>
* Default setupDatabase to false
* Rename variable
* Set default config db parameters for server
* Remove config db parameters from the env file
* Remove unnecessary environment statements
* Hide config persistence factory (#4772)
* Remove CONFIG_DATABASE_HOST
* Use builder in the test
* Simplify config persistence builder
* Clarify config db connection readiness
* Format code
* Add logging
* Fix typo
Co-authored-by: Christophe Duong <christophe.duong@gmail.com>
* Add a config_id only index
* Reuse record insertion code
* Add id field name to config schema
* Support data loading from legacy config schemas
* Log missing logs in migration test
* Move airbyte configs table to separate directory
* Update exception message
* Dump specific tables from the job database
* Remove postgres specific uuid extension
* Comment out future branch
* Default configs db variables to empty
When defaulting them to the jobs db variables, it somehow does not work.
* Log inserted config records
* Log all db write operations
* Add back config db variables in env file to mute warnings
* Log connection exception to debug flaky e2e test
* Leave config db variables empty
`.env` file does not support variable expansion.
Co-authored-by: Christophe Duong <christophe.duong@gmail.com>
Co-authored-by: Charles <giardina.charles@gmail.com>
