test: Add a gc for integration branches

[utam0k]

Description

Check for any remaining integration tests previously run before starting the test. This reduces wasteful preview environments.

Related Issue(s)

Relaates https://github.com/gitpod-io/gitpod/issues/12248#issuecomment-1246566840

How to test

1. Appropriately short timeouts to simplify testing
2. Create a branch for the test

$ branch="wk-inte-test/$(date +%Y%m%d%H%M%S)"
$ git branch $branch
$ git push origin $branch 

3. Run the integration test and check it

e.g. https://werft.gitpod-dev.com/job/gitpod-custom-to-gc-inte-br.5

Release Notes

NONE

Documentation

No

Werft options:

• [x] /werft with-preview
• [x] /werft with-integration-tests=workspace Valid options are all, workspace, webapp, ide

[utam0k]

/werft with-integration-tests=workspace

:-1: unknown command: with-integration-tests=workspace Use /werft help to list the available commands

[utam0k]

/werft run with-integration-tests=workspace

:+1: started the job as gitpod-build-to-gc-inte-br.2 (with .werft/ from main)

[werft-gitpod-dev-com[bot]]

started the job as gitpod-build-to-gc-inte-br.3 because the annotations in the pull request description changed (with .werft/ from main)

[utam0k]

/werft with-integration-tests=ide

:-1: unknown command: with-integration-tests=ide Use /werft help to list the available commands

[utam0k]

/werft run with-integration-tests=ide

:+1: started the job as gitpod-build-to-gc-inte-br.4 (with .werft/ from main)

[werft-gitpod-dev-com[bot]]

started the job as gitpod-build-to-gc-inte-br.6 because the annotations in the pull request description changed (with .werft/ from main)

[werft-gitpod-dev-com[bot]]

started the job as gitpod-build-to-gc-inte-br.7 because the annotations in the pull request description changed (with .werft/ from main)

[werft-gitpod-dev-com[bot]]

started the job as gitpod-build-to-gc-inte-br.10 because the annotations in the pull request description changed (with .werft/ from main)

[utam0k]

Out of curiosity, why the clean-up remote branch does not work sometimes?

job's timeout😭

[jenting]

Out of curiosity, why the clean-up remote branch does not work sometimes?

job's timeout😭

We can also increase the timeout from 120 mins to more because we will add more tests. Or we could separate the workspace component integration test into five jobs to cease the chance that job timeout happens.

[utam0k]

Out of curiosity, why the clean-up remote branch does not work sometimes?

job's timeout😭

We can also increase the timeout from 120 mins to more because we will add more tests. Or we could separate the workspace component integration test into five jobs to cease the chance that job timeout happens.

I will create an issue about it. If you have ideas, please let me know there.

[jenting]

/werft run

:+1: started the job as gitpod-build-to-gc-inte-br.14 (with .werft/ from main)

[utam0k]

@jenting rebased from man

[jenting]

@jenting rebased from man

The latest error comes this PR, and I left a comment https://github.com/gitpod-io/gitpod/pull/13241#issuecomment-1257430882

[werft-gitpod-dev-com[bot]]

started the job as gitpod-build-to-gc-inte-br.16 because the annotations in the pull request description changed (with .werft/ from main)

[utam0k]

/werft run

:+1: started the job as gitpod-build-to-gc-inte-br.17 (with .werft/ from main)