As it also catches pushes to branches which then cause duplicate execution on PR creation: once for the branch push and once for the PR create from the branch. This may need revisiting if we want to support PRs from forks.
The last commit fixed the issue by preventing accidental Droplet resize between Krill configure and Krill test. Re-enable undeploy and disable trigger by comment.
Temporarily disable undeploy while investigating failure to connect to remote Docker daemon.
Also attempt to print the output docker-compose ps and docker-compose logs if the build fails.
- Remove the debug print statement.
- Don't use ${GITHUB_WORKSPACE} in `working-directory` as perhaps the variable cannot be resolved at that time and so fails to correctly set the CWD?
- Temporarily allow the E2E test to be triggered by an issue comment so that minor issues with migrating it from the rpki-deploy repo can be resolved without unnecessary commits just to trigger the build.
- Debug print the current working directory to find out why the build was unable to find the Dockerfile.
- Be explicit about the paths to use.
