CI: временно закрепить buildkit v0.30.0 для Docker-образов

[sfaqer]

Временный обход для #1752: образы собираются отдельным buildx-сборщиком на moby/buildkit:v0.30.0 (runc 1.3.5, до регрессии). Когда на сервере обновят ядро или выйдет buildkit с runc 1.5.1+, правку нужно откатить.

Build v2 выполняется только на develop и release/latest, поэтому в сборке PR этот код не запускается. Проверится первой сборкой develop после слияния.

🤖 Generated with Claude Code

Summary by CodeRabbit

• Chores
  • Updated the container image publishing workflow to use a newer image-building environment. Existing image build options and outputs remain unchanged; there are no user-facing changes.

[coderabbitai]

Navigate logical layers of code changes, visualize relationships, and explore their blast radius.

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Advanced

Run ID: 93c21d6f-a668-49ce-8e02-33aae41355a8

📥 Commits

Reviewing files that changed from the base of the PR and between 270202a and 20bd057.

📒 Files selected for processing (1)

• Jenkinsfile

Included review availability: This review used your included allowance. Your plan provides up to 4 included reviews per hour; 2 remain after this review.

---

📝 Walkthrough

Walkthrough

The Jenkins Docker image publishing step now checks for a named Buildx builder and creates it with BuildKit v0.30.0 when absent. It passes the builder to the image build and retains the existing build options.

Changes

Docker image publishing

Layer / File(s)	Summary
Builder setup and image build Jenkinsfile	publishDockerImage checks for the named Buildx builder and creates it with BuildKit v0.30.0 if it is absent. The image build uses that builder and retains its existing options.

Priority: ➖ Normal

Estimated code review effort: 2 (Simple) | ~5 minutes

Change: Bug fix

Suggested reviewers: evilbeaver

Merge Risk: ⚪ Minimal · up to 20bd0

No actionable merge-blocking risk is established. The publishing build has not been observed here, so normal validation remains appropriate.

Architecture Summary

Architecture risk: 🔵 Low · up to 20bd0

The change affects 1 system.

Changed systems: Jenkinsfile

Architecture concerns
No architecture-level concerns identified.

Review details

Systems and components

• observed — Jenkinsfile (service) was modified; 1 changed file maps to changed impact.

Before / after behavior

• observed — Modified behavior in Jenkinsfile: publishDockerImage now selects a named Buildx builder using BuildKit v0.30.0, creating it with the corresponding BuildKit image if inspection fails, and passes the builder to docker.build. The existing build options are retained.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly describes the main change: temporarily pinning BuildKit v0.30.0 for Docker image builds in CI.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create a new PR

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}