Files
agile.zhou 9580a274e3 ci: remove redundant build-reactapp job from publish and test-cd
The Dockerfile now builds the React admin UI itself in a dedicated
ui-build stage (added in #240), so building it again in a separate CI
job and shipping the result via artifact was doing the same work twice
per release — and the in-Docker build silently won anyway.

Dropping the CI job leaves a single UI build path and keeps
'docker build .' reproducible outside of CI.

master-ci / master-pr-ci keep their build-reactapp job: those are
compile-only checks that gate frontend errors on PRs and never produce
an artifact. release-xxx keeps its job too, since its zip release
artifact comes from 'dotnet publish' and never goes through Docker.
2026-07-26 22:29:47 +08:00

53 lines
1.4 KiB
YAML

name: master test tag release workflow
on:
push:
paths-ignore:
- '**/*.md'
- '**/*.yml'
tags:
- 'test-*'
workflow_dispatch:
jobs:
# The React admin UI is built inside the Dockerfile (ui-build stage), so there
# is no separate build-reactapp job here.
build-dotnet-push-to-hub:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- name: setup .net
uses: actions/setup-dotnet@v4
with:
dotnet-version: |
8.0.x
9.0.x
10.0.x
- name: Install dependencies
run: dotnet restore
- name: Build
run: dotnet build --configuration Release --no-restore
- name: Push to Docker Hub
uses: docker/build-push-action@v1
with:
username: ${{ secrets.DOCKER_HUB_NAME }}
password: ${{ secrets.DOCKER_HUB_PASSWORD }}
repository: kklldog/agile_config
tags: test
- name: Login to ACR and push
uses: aliyun/acr-login@v1
with:
login-server: https://registry.cn-shanghai.aliyuncs.com
username: "${{ secrets.ALI_REGISTRY_USERNAME }}"
password: "${{ secrets.ALI_REGISTRY_PASSWORD }}"
- name: Build and push image
env:
IMAGE_TAG: test
run: |
docker build -t registry.cn-shanghai.aliyuncs.com/kklldog/agile_config:$IMAGE_TAG .
docker push registry.cn-shanghai.aliyuncs.com/kklldog/agile_config:$IMAGE_TAG