更新 .github/workflows/buidl_and_push_ghcr.yml
This commit is contained in:
101
.github/workflows/buidl_and_push_ghcr.yml
vendored
101
.github/workflows/buidl_and_push_ghcr.yml
vendored
@@ -1,53 +1,72 @@
|
|||||||
name: Docker Image CI
|
name: Gitea CI/CD for Helm Deployment
|
||||||
|
|
||||||
on:
|
on:
|
||||||
|
workflow_dispatch:
|
||||||
push:
|
push:
|
||||||
branches:
|
branches:
|
||||||
- main
|
- main
|
||||||
|
|
||||||
jobs:
|
jobs:
|
||||||
build:
|
build-and-push:
|
||||||
runs-on: ubuntu-latest
|
# 请将 'ubuntu-latest' 替换为您的 Gitea runner 标签, 例如: 'self-hosted, dind, rootless'
|
||||||
|
runs-on: ubuntu-latest
|
||||||
steps:
|
steps:
|
||||||
- name: Checkout code
|
- name: Checkout code
|
||||||
uses: actions/checkout@v4
|
uses: actions/checkout@v3
|
||||||
|
|
||||||
- name: Wait for and verify Docker-in-Docker (DIND) connection
|
- name: Set up Docker Buildx
|
||||||
run: |
|
uses: docker/setup-buildx-action@v3
|
||||||
echo "Waiting for Docker daemon to be ready..."
|
|
||||||
while ! docker info > /dev/null 2>&1; do
|
|
||||||
echo -n "."
|
|
||||||
sleep 1
|
|
||||||
done
|
|
||||||
echo "\nDocker daemon is ready!"
|
|
||||||
docker info
|
|
||||||
|
|
||||||
# 设置 Docker Buildx
|
- name: Log in to Gitea Container Registry
|
||||||
# 使用 driver: docker 以复用现有的 Docker 守护进程,避免在 Rootless 环境下挂载 socket 失败
|
uses: docker/login-action@v3
|
||||||
- name: Set up Docker Buildx
|
with:
|
||||||
uses: docker/setup-buildx-action@v3
|
# 请将 'gitea.example.com' 替换为您的 Gitea 实例 URL
|
||||||
with:
|
registry: gitea.173114.xyz
|
||||||
driver: docker
|
username: ${{ gitea.actor }}
|
||||||
|
# Gitea 会为工作流提供一个临时令牌用于访问包
|
||||||
|
password: ${{ secrets.GITEA_TOKEN }}
|
||||||
|
|
||||||
# 登录 Gitea 容器镜像库
|
- name: Build and push Docker image
|
||||||
- name: Log in to Gitea Container Registry
|
run: |
|
||||||
uses: docker/login-action@v3
|
# Gitea 仓库中的镜像名称
|
||||||
with:
|
IMAGE_NAME="gitea.173114.xyz/${{ gitea.owner }}/my-docs"
|
||||||
# 您的 Gitea 实例地址,请在 Gitea 仓库的 Secrets 中设置 GITEA_REGISTRY_URL
|
echo "Pushing to: $IMAGE_NAME"
|
||||||
registry: ${{ secrets.GITEA_REGISTRY_URL }}
|
docker build . --file Dockerfile \
|
||||||
username: ${{ gitea.actor }}
|
--tag "$IMAGE_NAME:latest" \
|
||||||
# 请在 Gitea 仓库的 Secrets 中创建一个具有包读写权限的 GITEA_TOKEN
|
--tag "$IMAGE_NAME:${{ gitea.sha }}"
|
||||||
password: ${{ secrets.GITEA_TOKEN }}
|
docker push "$IMAGE_NAME:latest"
|
||||||
|
docker push "$IMAGE_NAME:${{ gitea.sha }}"
|
||||||
|
|
||||||
# 构建并推送 Docker 镜像
|
deploy:
|
||||||
- name: Build and push Docker image
|
# 请将 'ubuntu-latest' 替换为您的 Gitea runner 标签
|
||||||
run: |
|
runs-on: ubuntu-latest
|
||||||
# 镜像名格式为:<Gitea 实例地址>/<所有者>/<仓库名>
|
needs: build-and-push
|
||||||
IMAGE_NAME="${{ secrets.GITEA_REGISTRY_URL }}/${{ gitea.repository_owner }}/my-docs"
|
steps:
|
||||||
echo "Pushing to: $IMAGE_NAME"
|
- name: Checkout code
|
||||||
docker build . --file Dockerfile \
|
uses: actions/checkout@v3
|
||||||
--tag "$IMAGE_NAME:latest" \
|
|
||||||
--tag "$IMAGE_NAME:${{ gitea.sha }}"
|
- name: Set up Kubeconfig
|
||||||
docker push "$IMAGE_NAME:latest"
|
run: |
|
||||||
docker push "$IMAGE_NAME:${{ gitea.sha }}"
|
mkdir -p $HOME/.kube
|
||||||
|
echo "${{ secrets.KUBE_CONFIG }}" > $HOME/.kube/config
|
||||||
|
chmod 600 $HOME/.kube/config
|
||||||
|
# KUBE_CONFIG应该是您的 kubeconfig 文件的 base64 编码内容
|
||||||
|
# 请在您的 Gitea 仓库设置中添加此 secret
|
||||||
|
if: ${{ secrets.KUBE_CONFIG != '' }}
|
||||||
|
|
||||||
|
- name: Set up Helm
|
||||||
|
uses: azure/setup-helm@v3
|
||||||
|
with:
|
||||||
|
# 如果需要,可以指定 Helm 版本, 例如: 'v3.8.0'
|
||||||
|
version: 'latest'
|
||||||
|
|
||||||
|
- name: Deploy with Helm
|
||||||
|
run: |
|
||||||
|
# 假设您的 Helm chart 位于 'helm/my-docs' 目录中
|
||||||
|
# 请将 'my-docs-release' 替换为您期望的 Helm release 名称
|
||||||
|
IMAGE_NAME="gitea.example.com/${{ gitea.owner }}/my-docs"
|
||||||
|
helm upgrade --install my-docs-release ./helm/my-docs \
|
||||||
|
--namespace my-docs-ns \
|
||||||
|
--create-namespace \
|
||||||
|
--set image.repository="$IMAGE_NAME" \
|
||||||
|
--set image.tag="${{ gitea.sha }}"
|
||||||
|
|||||||
Reference in New Issue
Block a user