Closed mgencur closed 2 months ago
/retest Wondering, why the GH workflows are not triggered :thinking:
Wondering, why the GH workflows are not triggered
Not sure which workflows you mean or where.
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: mgencur, pierDipi
The full list of commands accepted by this bot can be found here.
The pull request process is described here
Wondering, why the GH workflows are not triggered
Not sure which workflows you mean or where.
Generating Konflux files is part of "Generate CI Config"
Generating Konflux files is part of "Generate CI Config"
Yes, but these workflows (not even the unit tests) were triggered at that time. But as the run later as it seems, we're fine
Related to https://issues.redhat.com/browse/SRVCOM-3255
When serverless-operator includes imageOverrides in this format:
The following build-args will be generated for Buildah in .tekton/docker-build.yaml when generating Konflux configurations:
If Tekton pipelines are being generated for midstream branch that doesn't have a corresponding serverless-operator branch, the "guessed" branch will be used for the
VERSION
(e.g. at this point forrelease-v1.15
of Eventing, theVERSION
will berelease-1.35
The imageOverrides can later specify production-ready base images that will replace the "CI" images when building with Konflux.