This enables all slash commands to also work on PRs created from forks. This will not run CI on PRs coming from a fork. There are unfortunately some limitations around injecting secrets in pull_request actions, which I described in detail in this comment.
I've done most of the testing for this in https://github.com/timroes/github-actions-test to test out that the context are set the way I'd expect them.
There's one risk: if any of the actual build scripts called by one of the slash commands would use this repository hard-coded they might fail. I've tried to search through the whole code base and don't believe this is the case.
* Revert "Rm flaky test (#9628)"
This reverts commit 16133cf5e7.
* Restore the acceptance test running with the new scheduler
* Add timeout
* Isolate the new acceptance test
* Update github action name
* Attemptp to fix checkpointing
* Check the state retrieval instead of the existance of the workflow
* fix build
* Add concurrent list for test
* Do not wait for the workflow to be potentially destroy
* Silencely ignore the cancel exception
* Format
* Trigger build
* format
* Remove unrelated changes
* Update acceptance
* Try to fix race condition
* Try to slow down the connection
* Disable test
* Move the sleep
* Rm useless sleep
* Fix missing return
* add repeated
* try using infinite feed source for cancellation test
* set limits on infinite feed source
* misunderstood waitForJob, now correctly waiting for job to be in RUNNING
* clean up PR, DRY create definition methods, clearer method name for waiting on job
* fix acceptance tests action name
* fix imports
* more cleanup
* revert temporalClient do-while change
* fix workflow step names
Co-authored-by: Benoit Moriceau <benoit@airbyte.io>
* 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
* feat: add publish-external command to slash commands to publish external connector images
* fix: publish only stpec to cache
* fix: according to new script changes
* fix: removed tox installation
* fix: version is not read from command
* Add a job notification
The new scheduler was missing a notification step after the job is done.
This is needed in order to report the number of record of a sync.
* Acceptance test with the new scheduler
Add a new github action task to run the acceptances test with the new scheduler
* Retry if the failure
* PR comments
* Download spark jdbc driver in build cmd
* Download jdbc driver in ci integration test
* Update comments
* Set up cloud sdk
* Add comments
* Download jdbc driver from databricks directly
* Update readme
* Use unzip command
* Install unzip for databricks
* Add databricks build status
* Close database
* Log more error information
* Close database when checking connection
* Update spec
* updated ci performance test sh script
* updated ci performance test sh script
* set all params to one arg
* set all params to one arg
* set all params to one arg
* set all params to one arg
* set all params to one arg
* set all params to one arg
* set all params to one arg
* set all params to one arg
* set all params to one arg
* set all params to one arg
* set all params to one arg
* set all params to one arg
* set all params to one arg
* set all params to one arg
* set all params to one arg
* set all params to one arg
* set all params to one arg
* set all params to one arg
* set all params to one arg
* set all params to one arg
* set all params to one arg
* set all params to one arg
* set all params to one arg
* set all params to one arg
* set all params to one arg
* set all params to one arg
* set all params to one arg
* set all params to one arg
* set all params to one arg
* set all params to one arg
* set all params to one arg
* set all params to one arg
* set all params to one arg
* set all params to one arg
* set all params to one arg
* set all params to one arg
* set all params to one arg
* run tests
* update ci creds
* update performance test yaml file
* update performance test yaml file
* update performance test yaml file
* update performance test yaml file
* update performance test sh file
* update performance test sh file
* update performance test sh file
* update performance test sh file
* update java to 17 version in yaml file for performance tests
* update java to 17 version in yaml file for performance tests
* update java to 17 version in yaml file for performance tests
* update java to 17 version in yaml file for performance tests
* update java to 17 version in yaml file for performance tests
* clean test logs
* remove test logs
* remove test logs
* remove test logs
* return performance test logs
* add readme by performance tests
