-
Notifications
You must be signed in to change notification settings - Fork 0
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
quality: parameterize sdk and test data branches #72
Conversation
|
||
workflow_dispatch: | ||
|
||
workflow_call: |
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.
Allows specifying branches when used as a reusable workflow
branches: [main] | ||
branches: [main, tp/**] | ||
|
||
workflow_dispatch: |
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.
Used to allow dispatching via web API (remotely triggered test run when changes are made to sdk-test-data
)
@@ -21,6 +37,8 @@ jobs: | |||
steps: | |||
- uses: actions/checkout@v4 | |||
with: | |||
repository: Eppo-exp/sdk-common-jdk |
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.
explicitly specify the repo and ref otherwise, when run as a reusable workflow in another repo, this would not checkout the java-common SDK as required
@@ -40,7 +40,7 @@ test-data: | |||
mkdir -p ${tempDir} | |||
git clone -b ${branchName} --depth 1 --single-branch ${githubRepoLink} ${gitDataDir} | |||
cp -r ${gitDataDir}/ufc ${testDataDir} | |||
rm ${testDataDir}/ufc/bandit-tests/*.dynamic-typing.json | |||
rm -f ${testDataDir}/ufc/bandit-tests/*.dynamic-typing.json || true |
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.
bumped into this failing when I was doing some local testing that involved temporarily deleting most of the test data/cases. We shouldn't bump over this in any real scenario but no need to have this fail at any rate
"https://us-central1-eppo-qa.cloudfunctions.net/serveGitHubRacTestFile"; | ||
private static final String TEST_HOST = |
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.
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.
π
@@ -32,4 +50,4 @@ jobs: | |||
gpg-passphrase: ${{ secrets.GPG_PASSPHRASE }} | |||
|
|||
- name: Run tests | |||
run: make test | |||
run: make test branchName=${TEST_DATA_BRANCH} |
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.
π₯
ποΈ Fixes FF-3560 towards FF-3085
π―ββοΈ Related PRs
Motivation
Changes are often made to the sdk-test-data repository to capture new behaviours, bugs and edge cases. When these changes are pushed to
main
, the SDKs are cloned locally (locally to the github action running) and their respective tests are run. These tests are set up and run by copies of the SDK test workflows - see sdk-test-data workflow. There are a number of limitations to this setup:sdk-test-data
Description of Changes
This change
π - Each SDK's testing workflow is enhanced into a reusable workflow, exposing parameters for SDK branch and the sdk-test-data branch to use in testing.
External to this Change
sdk-test-data has two testing workflows.