This workflow runs the ESLint.
The workflow:
- Checks out code
- Invokes
make lint -C testing/e2e/skr
This workflow checks for broken links in all Markdown files. It is triggered:
- As a periodic check that runs daily at midnight on the main branch in the repository
- On every pull request
See Kyma Environment Broker Release Pipeline to learn more about the release workflow.
This workflow creates a PR to the management-plane-charts
repository with the given KEB release version. The default version is the latest KEB release.
This workflow creates a new KEB release and then promotes it to the development environment. It first runs the release workflow, and then creates a PR to the management-plane-charts
repository with the given KEB release version.
This workflow is triggered by PRs on the main
branch. It checks the labels on the PR and requires that the PR has exactly one of the labels listed in this file.
This workflow calls the reusable workflow with unit tests. Besides the tests, it also runs Go-related checks and Go linter.
This workflow runs the Govulncheck.
This workflow builds images.
This workflow calls the reusable workflow to install the KEB chart with the new images in the k3s cluster.
This workflow enables the auto-merge functionality on a PR that is not a draft.
This workflow checks if all jobs, except those excluded in the workflow configuration, have passed. If the workflow is triggered by a PR where the author is the kyma-gopher-bot
, the workflow ends immediately with success.
This workflow runs a validation of database migrations performed by Schema Migrator.
The workflow:
- Checks out code
- Invokes the validation script.
There are reusable workflows created. Anyone with access to a reusable workflow can call it from another workflow.
This workflow runs the unit tests.
No parameters are passed from the calling workflow (callee).
The end-to-end unit tests use a PostgreSQL database in a Docker container as the default storage solution, which allows
the execution of SQL statements during these tests. You can switch to in-memory storage
by setting the DB_IN_MEMORY_FOR_E2E_TESTS environment variable to true
. However, by using PostgreSQL, the tests can effectively perform
instance details serialization and deserialization, providing a clearer understanding of the impacts and outcomes of these processes.
The workflow:
- Checks out code and sets up the cache
- Sets up the Go environment
- Invokes
make go-mod-check
- Invokes
make test
This workflow installs the KEB chart in the k3s cluster. You pass the following parameters from the calling workflow:
Parameter name | Required | Description |
---|---|---|
last-k3s-versions | no | number of most recent k3s versions to be used for tests, default = 1 |
release | no | determines if the workflow is called from release, default = true |
version | no | chart version, default = 0.0.0.0 |
The workflow:
- Checks if the KEB chart is rendered successfully by Helm
- Fetches the last-k3s-versions tag versions of k3s releases
- Prepares the last-k3s-versions k3s clusters with the Docker registries using the list of versions from the previous step
- Creates required namespaces
- Installs required dependencies by the KEB chart
- Installs the KEB chart in the k3s cluster using
helm install
- Waits for all tests to finish