Configure Cross-Repo Build Mechanism Against Testing Library #58
Description
Overview
Right now, we have 2 separate repositories for Python:
- This repository - https://github.com/aws/aws-durable-execution-sdk-python
- The testing library - https://github.com/aws/aws-durable-execution-sdk-python-testing
The testing library takes a hard dependency on the python language SDK, so changes in the language SDK may inadvertently break the testing library. Moreover, the testing library has a set of examples which deploy to run integration tests to verify end to end functionality.
Right now, we have a mechanism in the testing library to run integration tests against a specific branch of the language SDK. See the GitHub workflow - it parses the PR description for the specific branch of the Language SDK to use. This defaults to main, but can be overridden in a PR if your change requires specific changes in the language SDK to build properly.
We don't have a mechanism that goes the other way. Specifically, we want to trigger the build + integration tests in the testing library repository when we make changes to the python language SDK. This is needed so that we can run integration tests when we make changes to the python language SDK. This should be set up in such a way that you can target a specific branch in the testing library too for changes that require cross-repository coordination.
Acceptance Criteria
- When we open a PR against this repository, we trigger the build and integration tests against the language SDK.
- The results of the integration tests are visible in this PR. I'm not sure if triggering a workflow cross-repository will show up in the "Actions" of the PR. Alternatively we can look at using a test reporter that will post on the PR like https://github.com/ctrf-io/github-test-reporter