Paul Meyer
4020e7840a
ci: always use tee -a instead of redirecting
...
into GITHUB_OUTPUT
Signed-off-by: Paul Meyer <49727155+katexochen@users.noreply.github.com>
2023-04-17 12:08:42 +02:00
Paul Meyer
860d72a083
ci: reduce number of steps with continue-on-error ( #1593 )
...
Signed-off-by: Paul Meyer <49727155+katexochen@users.noreply.github.com>
2023-04-14 18:50:58 +02:00
Paul Meyer
dea41bd1ed
ci: refactor e2e test failure notifications ( #1625 )
...
Signed-off-by: Paul Meyer <49727155+katexochen@users.noreply.github.com>
2023-04-12 16:06:26 +02:00
Moritz Sanft
6ba294e175
ci: separate e2e permissions ( #1555 )
...
* split e2e test iam create / create perms
* remove global Azure credentials
* remove unnecessary azure actions
* use UUID
* fix e2e upgrade test
* rename create inputs
* remove continue-on-error for resource deletion
* de-exclude verify test
* fix exclude
* fix release e2e test
---------
Co-authored-by: Nils Hanke <nils.hanke@outlook.com>
2023-04-12 13:24:13 +02:00
Malte Poll
2b962598bf
deps: update go to 1.20.3 ( #1622 )
2023-04-06 16:36:07 +02:00
renovate[bot]
8f17e4b9df
deps: update actions/setup-go action to v4 ( #1605 )
...
Co-authored-by: katexochen <katexochen@users.noreply.github.com>
2023-04-04 11:06:30 +02:00
Paul Meyer
00efc30e24
ci: fix empty image input of verify e2e on release ( #1604 )
...
* ci: fix empty image input of verify e2e on release
* ci: increase parallelism of e2e release workflow
Signed-off-by: Paul Meyer <49727155+katexochen@users.noreply.github.com>
2023-04-04 10:47:26 +02:00
Otto Bittner
b5ce95a7a1
ci: do not run tests on macOS ( #1595 )
...
only run two tests on macOS as a simple smoketest
2023-04-03 17:47:21 +02:00
renovate[bot]
5dad9bfad7
deps: update GitHub action dependencies ( #1591 )
...
Co-authored-by: Paul Meyer <49727155+katexochen@users.noreply.github.com>
2023-04-03 16:36:43 +02:00
Otto Bittner
1dd5eae594
ci: do not skip e2e-weekly if trigger is successful ( #1584 )
2023-04-03 13:40:42 +02:00
Otto Bittner
4df33b93fe
ci: add e2e-test-release workflow
...
This workflow is used to run e2e tests in
preparation to a release.
It is triggered by the successful completion of
the release workflow.
Also trigger e2e-mini through the release
workflow completion.
This makes restarting the tests easier if
they fail during release preparation.
Co-authored-by: stdoutput <moritz.sanft@outlook.de>
2023-04-03 11:35:39 +02:00
