migrate CICD-Pipeline to GitHub-Actions #12592

ccwienk · 2025-07-22T20:11:52Z

see: https://gardener.github.io/cc-utils/github_actions.html

How to categorize this PR?

/area delivery
/kind technical-debt
/kind task

What this PR does / why we need it:

Which issue(s) this PR fixes:
Fixes #

Special notes for your reviewer:

As GitHub-Action will only become available after merging this pullrequest, please refer to, e.g. this run for checking on the pipeline.

Release note:

migrate CICD-Pipeline to GitHub-Actions

rfranzke · 2025-07-23T06:03:23Z

/assign @oliver-goetz

LucaBernstein · 2025-07-23T06:04:21Z

/cc @tobschli
as next release responsible.
We should probably wait until this week's release has been cut.
/hold

ccwienk · 2025-07-23T06:14:18Z

/cc @tobias Schlicht as next release responsible. We should probably wait until this week's release has been cut. /hold

@LucaBernstein : in the end, that's of course up to you. The underlying workflows have already been used for some releases in the past (e.g. for dashboard, and also some extensions). I do not think waiting for one more release will make a lot of a difference; if you like, I could drop the deletion of .ci/pipeline_definitions and .ci/component_descriptor, respectively. In that case, accepting this pullrequest will give you the option to use either concourse or GitHub-Actions for creating a release (so you might fallback to Concourse, if there should be any issues).

.github/workflows/upgrade-dependencies.yaml

LucaBernstein

Thank you for the PR, just one more question from my side @ccwienk 😃

.github/workflows/build.yaml

LucaBernstein · 2025-07-23T12:42:43Z

.github/workflows/release.yaml

+      mode: release
+
+  release-to-github-and-bump:
+    uses: gardener/cc-utils/.github/workflows/release.yaml@master


Do you cut releases in cc-utils or should we pin the references to some tag/hash to ensure reproducability and controlled updates?

Currently (as there is still some ongoing development), there is not yet a branching-model in place. For the time being, it might be considered to pin to commit-digests after release (such as to fixate release-branches), and remain on master for gardener/gardener's master-branch.

I will (have to) think of a proper release process, also considering usage for gh-tools/wdf; however, this is out-of scope for initial migration. Also, this is equivalent to concourse-pipelines, where - while there is a QA-step involved - there is also only ever one global pipeline-template-version 🫣

Now that I think of it, we could even include the commit-pinning into the release.yaml-workflow so that this will be done automatically upon release, as part of the release-commit. WDYT?

That's some ideas there, thanks for thinking about it.
Maybe later we will introduce versioning in the cc-utils once it's considered stable(r).
We could go with the as-is for now imho. Maybe, as you suggested, we could eventually pin the utils commit upon release.

ccwienk · 2025-07-24T06:12:35Z

/hold - need to add relase-assets

/unhold (done)

ccwienk · 2025-07-24T06:13:35Z

however:
/hold (so @LucaBernstein 's hold is not undone)

oliver-goetz

Thanks for moving the repo to github actions 🚀

.github/workflows/build.yaml

see: https://gardener.github.io/cc-utils/github_actions.html

LucaBernstein

/lgtm

gardener-prow · 2025-07-29T09:37:28Z

LGTM label has been added.

Git tree hash: 11e03491c1bf5252fe1755c02df186ee82a9c806

oliver-goetz

Okay, let's go 🤞
😄

/approve
/unhold

gardener-prow · 2025-07-29T13:35:23Z

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: oliver-goetz

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

~~OWNERS~~ [oliver-goetz]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

oliver-goetz · 2025-07-29T13:37:12Z

I had to merge the PR manually, because it is updating Github workflows.

ialidzhikov · 2025-07-29T13:44:45Z

The workflow is not valid. In .github/workflows/non-release.yaml (Line: 8, Col: 11): Error from called workflow gardener/gardener/.github/workflows/build.yaml@a13c79fc998fafaa135083122d82b590f4723eb9 (Line: 176, Col: 9): Job 'gardenadm' depends on unknown job 'test'.

The script does not seem to be used after gardener#12592.

* Clean up the obsolete `.ci/set_dependency_version` script The `.ci/set_dependency_version` script is part of the [component upgrade contract](https://gardener.github.io/cc-utils/traits/update_component_deps.html). However, the gardener/gardener repository no longer uses concourse. Even before than, I am not sure if this component upgrade contract was used for the gardener/gardener repo after the introduction of Renovate for updating referenced OCI images. The `hack/.ci/set_dependency_version` script is still preserved as it is still reused by the extension repositories. See also the [ocm-upgrade action](https://github.com/gardener/cc-utils/blob/master/.github/actions/ocm-upgrade/action.yaml). * Clean up the obsolete `.ci/verify` script The script does not seem to be used after #12592.

* Clean up the obsolete `.ci/set_dependency_version` script The `.ci/set_dependency_version` script is part of the [component upgrade contract](https://gardener.github.io/cc-utils/traits/update_component_deps.html). However, the gardener/gardener repository no longer uses concourse. Even before than, I am not sure if this component upgrade contract was used for the gardener/gardener repo after the introduction of Renovate for updating referenced OCI images. The `hack/.ci/set_dependency_version` script is still preserved as it is still reused by the extension repositories. See also the [ocm-upgrade action](https://github.com/gardener/cc-utils/blob/master/.github/actions/ocm-upgrade/action.yaml). * Clean up the obsolete `.ci/verify` script The script does not seem to be used after gardener#12592.

gardener-prow bot added area/delivery Delivery related kind/technical-debt Something that is only solved on the surface, but requires more (re)work to be done properly kind/task General task cla: yes Indicates the PR's author has signed the cla-assistant.io CLA. labels Jul 22, 2025

gardener-prow bot requested review from acumino and rfranzke July 22, 2025 20:12

gardener-prow bot added the size/L Denotes a PR that changes 100-499 lines, ignoring generated files. label Jul 22, 2025

ccwienk force-pushed the master branch 3 times, most recently from 4df8de2 to 2ea1476 Compare July 23, 2025 05:06

This comment was marked as outdated.

Sign in to view

gardener-prow bot assigned oliver-goetz Jul 23, 2025

gardener-prow bot requested a review from tobschli July 23, 2025 06:04

gardener-prow bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jul 23, 2025

ialidzhikov reviewed Jul 23, 2025

View reviewed changes

.github/workflows/upgrade-dependencies.yaml Outdated Show resolved Hide resolved

ccwienk force-pushed the master branch from 2ea1476 to 2d9f384 Compare July 23, 2025 07:12

LucaBernstein reviewed Jul 23, 2025

View reviewed changes

.github/workflows/build.yaml Show resolved Hide resolved

LucaBernstein reviewed Jul 23, 2025

View reviewed changes

ccwienk force-pushed the master branch from 2d9f384 to 26a6460 Compare July 23, 2025 16:15

This comment was marked as outdated.

Sign in to view

This comment was marked as resolved.

Sign in to view

ccwienk force-pushed the master branch from 26a6460 to a7bb157 Compare July 23, 2025 18:13

This comment was marked as outdated.

Sign in to view

gardener-prow bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jul 24, 2025

oliver-goetz reviewed Jul 25, 2025

View reviewed changes

.github/workflows/build.yaml Outdated Show resolved Hide resolved

ccwienk force-pushed the master branch from a7bb157 to 47e6e93 Compare July 29, 2025 05:45

gardener-prow bot removed the lgtm Indicates that a PR is ready to be merged. label Jul 29, 2025

gardener-prow bot requested review from LucaBernstein and oliver-goetz July 29, 2025 05:45

ccwienk force-pushed the master branch 4 times, most recently from 14cec34 to a948e77 Compare July 29, 2025 06:00

migrate CICD-Pipeline to GitHub-Actions

987638e

see: https://gardener.github.io/cc-utils/github_actions.html

ccwienk force-pushed the master branch from a948e77 to 987638e Compare July 29, 2025 09:10

LucaBernstein reviewed Jul 29, 2025

View reviewed changes

gardener-prow bot added the lgtm Indicates that a PR is ready to be merged. label Jul 29, 2025

oliver-goetz approved these changes Jul 29, 2025

View reviewed changes

gardener-prow bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jul 29, 2025

gardener-prow bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jul 29, 2025

oliver-goetz merged commit a13c79f into gardener:master Jul 29, 2025
19 checks passed

oliver-goetz mentioned this pull request Jul 29, 2025

Fix gardenadm step in Github build workflow #12629

Merged

ialidzhikov mentioned this pull request Jul 30, 2025

Update the build badge from Concourse to GitHub Actions #12632

Merged

oliver-goetz mentioned this pull request Jul 30, 2025

Build artifacts only on head update of master and release branches #12636

Merged

This was referenced Aug 11, 2025

Migrate CICD-Pipeline to GitHub-Actions gardener/gardener-extension-shoot-rsyslog-relp#281

Merged

Migrate CICD-Pipelines to GitHub-Actions gardener/gardener-extension-registry-cache#420

Merged

ialidzhikov added a commit to ialidzhikov/gardener that referenced this pull request Aug 11, 2025

Clean up the obsolete .ci/verify script

c7eb3d8

The script does not seem to be used after gardener#12592.

ialidzhikov mentioned this pull request Aug 11, 2025

Clean up obsolete CI scripts #12705

Merged

migrate CICD-Pipeline to GitHub-Actions #12592

migrate CICD-Pipeline to GitHub-Actions #12592

Uh oh!

Conversation

ccwienk commented Jul 22, 2025

Uh oh!

This comment was marked as outdated.

This comment was marked as outdated.

rfranzke commented Jul 23, 2025

Uh oh!

LucaBernstein commented Jul 23, 2025

Uh oh!

ccwienk commented Jul 23, 2025

Uh oh!

Uh oh!

LucaBernstein left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

LucaBernstein Jul 23, 2025

Choose a reason for hiding this comment

Uh oh!

ccwienk Jul 23, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

ccwienk Jul 23, 2025

Choose a reason for hiding this comment

Uh oh!

LucaBernstein Jul 24, 2025

Choose a reason for hiding this comment

Uh oh!

This comment was marked as outdated.

This comment was marked as resolved.

This comment was marked as outdated.

ccwienk commented Jul 24, 2025

Uh oh!

ccwienk commented Jul 24, 2025

Uh oh!

oliver-goetz left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

LucaBernstein left a comment

Choose a reason for hiding this comment

Uh oh!

gardener-prow bot commented Jul 29, 2025

Uh oh!

oliver-goetz left a comment

Choose a reason for hiding this comment

Uh oh!

gardener-prow bot commented Jul 29, 2025

Uh oh!

Uh oh!

oliver-goetz commented Jul 29, 2025

Uh oh!

ialidzhikov commented Jul 29, 2025

Uh oh!

Uh oh!

ccwienk Jul 23, 2025 •

edited

Loading