Is your feature request related to a problem? Please describe.
When we have an environment that is already deployed, there is no need to trigger all of the matrix jobs and container builds again. For example, if we want to make a change to test behaviour and not hte underlying code due to a transient failure, at present we have to run all of the prior steps if a new commit is pushed.
Describe the solution you'd like
- Add a skip_deployment flag to the PR bot commands for /test and /test-extended
- Ensure this starts the workflow at e2e and smoke test jobs and skips all prior steps
Describe alternatives you've considered
Considered creating a separate E2E workflow just for running tests, however this may be more useful as we can drive it via pr bot commands.
Additional context
Add any other context or screenshots about the feature request here.
Is your feature request related to a problem? Please describe.
When we have an environment that is already deployed, there is no need to trigger all of the matrix jobs and container builds again. For example, if we want to make a change to test behaviour and not hte underlying code due to a transient failure, at present we have to run all of the prior steps if a new commit is pushed.
Describe the solution you'd like
Describe alternatives you've considered
Considered creating a separate E2E workflow just for running tests, however this may be more useful as we can drive it via pr bot commands.
Additional context
Add any other context or screenshots about the feature request here.