You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Goal is to introduce simplified, lightweight GH workflows as a balance between quality and development experience. GH workflows should be consistent between our projects. Idea is to introduce minimal testing on PR issued to main and to release branches that run only on k3d cluster. PR workflow should be fast and reliable. Main workflow beside tests running on k3d should introduce tests executed on gardener (AWS, GCP). Same approach should be applied on release workflow. Schedule workflow should run all available tests ran on k3d and Gardener AWS.
create / adjust pull workflow that builds own image, execute lint and unit tests, execute integration tests on k3d
create / adjust post workflow
create / adjust schedule workflow that builds image with image-builder, execute integration test, custom domain tests, upgrade tests, compatibility test, UI test and APIRule migration test on k3d, AWS, GCP
Description
Goal is to introduce simplified, lightweight GH workflows as a balance between quality and development experience. GH workflows should be consistent between our projects. Idea is to introduce minimal testing on PR issued to main and to release branches that run only on k3d cluster. PR workflow should be fast and reliable. Main workflow beside tests running on k3d should introduce tests executed on gardener (AWS, GCP). Same approach should be applied on release workflow. Schedule workflow should run all available tests ran on k3d and Gardener AWS.
ToDos [Developer]
The text was updated successfully, but these errors were encountered: