<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>CI/CD on Jermineの博客 </title>
    <link>https://Jermine.vdo.pub/tags/ci/cd/</link>
    <description>Recent content in CI/CD on Jermineの博客 </description>
    <generator>Hugo</generator>
    <language>zh-CN</language>
    <lastBuildDate>Mon, 15 Jun 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://Jermine.vdo.pub/tags/ci/cd/feed.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Jenkins 中使用 Buildah Push 推送镜像的三种认证方式</title>
      <link>https://Jermine.vdo.pub/docker/buildah-push-auth-in-jenkins/</link>
      <pubDate>Mon, 15 Jun 2026 00:00:00 +0000</pubDate>
      <guid>https://Jermine.vdo.pub/docker/buildah-push-auth-in-jenkins/</guid>
      <description>&lt;p&gt;在 Jenkins 容器中使用 &lt;code&gt;buildah push&lt;/code&gt; 推送镜像时，设置登录认证主要有三种方式。将凭证硬编码在命令里会带来严重的安全风险，因此在实际的 CI/CD 实践中，&lt;strong&gt;更推荐采用&amp;quot;登录 (Login) + 配置文件 (Authfile)&amp;ldquo;的方式&lt;/strong&gt;。&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
