These scripts can trigger a push, release, or workflow_dispatch event but they can do that depending on the e2e workflow file name. So we should be able to merge them.
We should probably refactor a bit so that there isn't too much hard-to-read code branching.
There are a few things that need to happen differently based on a few things:
Workflow:
- For nodejs workflows the Node package needs to be updated to bump the version.
- For all other tests we don't need to do anything special.
Event type:
These scripts can trigger a
push,release, orworkflow_dispatchevent but they can do that depending on the e2e workflow file name. So we should be able to merge them.e2e-create-release.sh: Currently used to createreleaseevents.e2e-dispatch.sh: currently used to createworkflow_dispatchevents.e2e-nodejs-push.sh: Currently used for Node.js builder e2e tests to generatepushto branch,pushto tag,release,create, andworkflow_dispatchevents.e2e-push-tag.sh: Currently used to createpushto tag events.e2e-push.sh: Currently used to generatepushto branch events.e2e-maven-push.sh- Currently used topushfor Maven builder testse2e-gradle-push.shupcoming in Add test for Gradle builder #270We should probably refactor a bit so that there isn't too much hard-to-read code branching.
There are a few things that need to happen differently based on a few things:
Workflow:
Event type:
e2e/<workflow-file>.txtand push it. This will allow us to filter the e2e test triggers to only trigger on that file. This will help us fix Canceling since a higher priority waiting request for 'e2e-nodejs-push-main-disttag-slsa3' exists #228.