Dev gradle ci

[livk-cloud]

Summary by Sourcery

更新 CI 配置以在 CircleCI 和 GitHub Actions 中包含 JDK 21 和 JDK 22 的构建。重构 Gradle 插件代码以提高可读性和一致性。

增强功能：

• 重构 Gradle 插件代码以提高可读性和一致性。

CI：

• 在 CircleCI 配置中添加 JDK 21 和 JDK 22 的新 CI 任务。
• 为 JDK 21 和 JDK 22 构建引入 GitHub Actions 工作流。

Original summary in English

Summary by Sourcery

Update CI configuration to include builds for JDK 21 and JDK 22 using both CircleCI and GitHub Actions. Refactor Gradle plugin code for better readability and consistency.

Enhancements:

• Refactor Gradle plugin code for improved readability and consistency.

CI:

• Add new CI jobs for JDK 21 and JDK 22 in CircleCI configuration.
• Introduce GitHub Actions workflows for JDK 21 and JDK 22 builds.

[sourcery-ai]

审核指南 by Sourcery

此 PR 通过用 GitHub Actions 工作流替换 CircleCI 配置来实现 CI 工作流改进，并在构建配置中包括了若干 Kotlin 代码优化。更改引入了 JDK 21 和 JDK 22 的并行 CI 测试，以及代码重构以提高 Gradle 构建脚本的可读性和可维护性。

未生成图表，因为更改看起来简单，不需要视觉表示。

文件级更改

更改	详情	文件
从 CircleCI 迁移到 GitHub Actions 用于 CI/CD	为 JDK 21 和 JDK 22 构建添加了单独的工作流文件 配置 GitHub Actions 使用 Temurin JDK 分发 在工作流中设置当前版本的 Gradle 移除原始 CircleCI 配置	.github/workflows/jdk21-ci.yml .github/workflows/jdk22-ci.yml .github/workflows/gradle.yml .circleci/config.yml
重构 Kotlin 构建配置代码以提高可维护性	使用方法引用简化 lambda 表达式 改进代码格式和缩进 使用 ZonedDateTime 而不是 Instant 增强时间处理 通过直接方法引用优化集合处理	buildSrc/src/main/kotlin/com/google/protobuf/gradle/ProtobufPlugin.kt buildSrc/src/main/kotlin/com/livk/boot/maven/DeployedPlugin.kt buildSrc/src/main/kotlin/com/livk/boot/compile/CompileArgsPlugin.kt buildSrc/src/main/kotlin/com/livk/boot/dependency/ManagementPlugin.kt buildSrc/src/main/kotlin/com/livk/boot/info/BootPlugin.kt

---

提示和命令

与 Sourcery 互动

• 触发新审核： 在拉取请求上评论 @sourcery-ai review。
• 继续讨论： 直接回复 Sourcery 的审核评论。
• 从审核评论生成 GitHub 问题： 通过回复审核评论请求 Sourcery 创建一个问题。
• 生成拉取请求标题： 在拉取请求标题的任何地方写 @sourcery-ai 以随时生成标题。
• 生成拉取请求摘要： 在拉取请求正文的任何地方写 @sourcery-ai summary 以随时生成 PR 摘要。您也可以使用此命令指定摘要应插入的位置。

自定义您的体验

访问您的仪表板以：

• 启用或禁用审核功能，例如 Sourcery 生成的拉取请求摘要、审核指南等。
• 更改审核语言。
• 添加、删除或编辑自定义审核说明。
• 调整其他审核设置。

获取帮助

• 联系我们的支持团队以获取问题或反馈。
• 访问我们的文档以获取详细指南和信息。
• 通过关注我们在 X/Twitter、LinkedIn 或 GitHub 上的 Sourcery 团队保持联系。

Original review guide in English

Reviewer's Guide by Sourcery

This PR implements CI workflow improvements by replacing CircleCI configuration with GitHub Actions workflows and includes several Kotlin code optimizations in the build configuration. The changes introduce parallel CI testing for both JDK 21 and JDK 22, along with code refactoring to improve readability and maintainability of the Gradle build scripts.

No diagrams generated as the changes look simple and do not need a visual representation.

File-Level Changes

Change	Details	Files
Migrated from CircleCI to GitHub Actions for CI/CD	Added separate workflow files for JDK 21 and JDK 22 builds Configured GitHub Actions to use Temurin JDK distribution Set up Gradle with current version in workflows Removed original CircleCI configuration	.github/workflows/jdk21-ci.yml .github/workflows/jdk22-ci.yml .github/workflows/gradle.yml .circleci/config.yml
Refactored Kotlin build configuration code for better maintainability	Simplified lambda expressions using method references Improved code formatting and indentation Enhanced time handling using ZonedDateTime instead of Instant Optimized collection processing with direct method references	buildSrc/src/main/kotlin/com/google/protobuf/gradle/ProtobufPlugin.kt buildSrc/src/main/kotlin/com/livk/boot/maven/DeployedPlugin.kt buildSrc/src/main/kotlin/com/livk/boot/compile/CompileArgsPlugin.kt buildSrc/src/main/kotlin/com/livk/boot/dependency/ManagementPlugin.kt buildSrc/src/main/kotlin/com/livk/boot/info/BootPlugin.kt

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time. You can also use
  this command to specify where the summary should be inserted.

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

嗨 @livk-cloud - 我已经审查了你的更改 - 这里有一些反馈：

总体评论：

• 考虑在 GitHub Actions 工作流中启用 Gradle 缓存以提高构建时间。你可以使用 actions/cache 操作为依赖项和构建输出添加缓存配置。

这是我在审查期间查看的内容

• 🟡 一般问题：发现 1 个问题
• 🟢 安全性：一切看起来都很好
• 🟢 测试：一切看起来都很好
• 🟢 复杂性：一切看起来都很好
• 🟢 文档：一切看起来都很好

---

Sourcery 对开源项目免费 - 如果你喜欢我们的评论，请考虑分享它们 ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{帮助我变得更有用！请在每条评论上点击 👍 或 👎，我将使用反馈来改进你的评论。}

Original comment in English

Hey @livk-cloud - I've reviewed your changes - here's some feedback:

Overall Comments:

• Consider enabling Gradle caching in the GitHub Actions workflows to improve build times. You can add cache configuration for both dependencies and build outputs using the actions/cache action.

Here's what I looked at during the review

• 🟡 General issues: 1 issue found
• 🟢 Security: all looks good
• 🟢 Testing: all looks good
• 🟢 Complexity: all looks good
• 🟢 Documentation: all looks good

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[sourcery-ai]

建议： 考虑为常见的 Gradle 设置步骤创建一个可重用的工作流

Gradle 设置步骤在 JDK21 和 JDK22 工作流之间重复。考虑创建一个可重用的工作流以减少重复并简化维护。

      - uses: ./.github/workflows/gradle-setup.yml

Original comment in English

suggestion: Consider creating a reusable workflow for common Gradle setup steps

The Gradle setup steps are duplicated between the JDK21 and JDK22 workflows. Consider creating a reusable workflow to reduce duplication and make maintenance easier.

      - uses: ./.github/workflows/gradle-setup.yml

[sonarqubecloud]

Quality Gate passed

Issues
2 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud