<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Jib on PlumePHP</title><link>https://plumephp.com/tags/jib/</link><description>Recent content in Jib on PlumePHP</description><generator>Hugo</generator><language>zh-CN</language><lastBuildDate>Wed, 30 Sep 2026 13:00:00 +0800</lastBuildDate><atom:link href="https://plumephp.com/tags/jib/index.xml" rel="self" type="application/rss+xml"/><item><title>GitHub Actions Java/JVM CI：Maven、Gradle、JaCoCo 与 Jib 容器化</title><link>https://plumephp.com/github-actions-java-jvm-ci/</link><pubDate>Wed, 30 Sep 2026 13:00:00 +0800</pubDate><guid>https://plumephp.com/github-actions-java-jvm-ci/</guid><description>&lt;blockquote&gt;
&lt;p&gt;JVM 项目的 CI 不仅要编译和测试，还要处理复杂的依赖图、多 JDK 兼容性、代码覆盖率报告和容器化发布。Maven 和 Gradle 的依赖缓存策略直接决定 CI 速度，JaCoCo 和 SonarCloud 提供质量门禁，Jib 让 Java 应用无需 Dockerfile 即可构建优化过的容器镜像。本文覆盖 JVM 生态完整的 GitHub Actions CI 方案。&lt;/p&gt;</description></item></channel></rss>