food-market/.forgejo/workflows/docker-web.yml
nns 1f19d7ca44
Some checks failed
CI / POS (WPF, Windows) (push) Waiting to run
CI / Backend (.NET 8) (push) Successful in 58s
CI / Web (React + Vite) (push) Successful in 34s
Docker API / Build + push API (push) Failing after 5s
Docker API / Deploy API on stage (push) Has been skipped
Docker Web / Build + push Web (push) Failing after 6s
Docker Web / Deploy Web on stage (push) Has been skipped
ci(docker): split into docker-api.yml + docker-web.yml — независимые pipeline'ы
В предыдущей попытке runner v6.2.2 не подружился с cross-job outputs —
job changes падал «'runs-on' key not defined in Docker Images/changes»
и оба следующих job уходили в skipped. Откатываю на надёжный путь:
два отдельных workflow с paths-фильтром на уровне триггера.

- docker-api.yml: триггерится на src/food-market.api/**,
  application/**, domain/**, infrastructure/**, shared/**, sln,
  Dockerfile.api, compose. Билдит buildx с registry-cache, пуллит
  и пересоздаёт ТОЛЬКО api (`docker compose up -d --no-deps api`).
- docker-web.yml: триггерится на src/food-market.web/**, Dockerfile.web,
  nginx.conf, compose. Делает то же для web.
- .env стенда теперь идемпотентный — оба тэга всегда :latest, после
  push образа buildx обновляет latest, pull тянет свежий.
- Telegram отдельные сообщения «stage api deployed» / «stage web
  deployed» с SHA — понятно что именно прилетело.

Push, который не задевает ни api/ ни web/ исходники (только md/docs),
вообще не запускает workflow — экономия очевидна.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-04-25 13:22:31 +05:00

98 lines
3 KiB
YAML

name: Docker Web
on:
push:
branches: [main]
paths:
- 'src/food-market.web/**'
- 'deploy/Dockerfile.web'
- 'deploy/nginx.conf'
- 'deploy/docker-compose.yml'
- '.forgejo/workflows/docker-web.yml'
workflow_dispatch:
env:
LOCAL_REGISTRY: 127.0.0.1:5001
jobs:
build:
name: Build + push Web
runs-on: [self-hosted, linux]
steps:
- uses: actions/checkout@v4
- name: Build + push (buildx with registry cache)
env:
SHA: ${{ github.sha }}
run: |
docker buildx create --use --name fmbuilder --driver docker-container 2>/dev/null \
|| docker buildx use fmbuilder
docker buildx build \
-f deploy/Dockerfile.web \
-t $LOCAL_REGISTRY/food-market-web:$SHA \
-t $LOCAL_REGISTRY/food-market-web:latest \
--cache-from type=registry,ref=$LOCAL_REGISTRY/food-market-web:buildcache \
--cache-to type=registry,ref=$LOCAL_REGISTRY/food-market-web:buildcache,mode=max \
--push .
deploy:
name: Deploy Web on stage
needs: build
runs-on: [self-hosted, linux]
steps:
- uses: actions/checkout@v4
- name: Update compose + .env
env:
PGPASS: ${{ secrets.STAGE_POSTGRES_PASSWORD }}
run: |
cat > /home/nns/food-market-stage/deploy/.env <<ENV
REGISTRY=127.0.0.1:5001
API_TAG=latest
WEB_TAG=latest
POSTGRES_PASSWORD=$PGPASS
ENV
cp deploy/docker-compose.yml /home/nns/food-market-stage/deploy/docker-compose.yml
- name: Pull + recreate web only
working-directory: /home/nns/food-market-stage/deploy
run: |
docker compose pull web
docker compose up -d --no-deps web
- name: Smoke /health
run: |
for i in 1 2 3 4 5 6; do
sleep 5
if curl -fsS http://127.0.0.1:8081/ -o /dev/null; then
echo "Web OK"
exit 0
fi
done
echo "Web smoke failed"
exit 1
- name: Notify Telegram on success
if: success()
env:
BOT: ${{ secrets.TELEGRAM_BOT_TOKEN }}
CHAT: ${{ secrets.TELEGRAM_CHAT_ID }}
SHA: ${{ github.sha }}
run: |
curl -sS -X POST "https://api.telegram.org/bot$BOT/sendMessage" \
--data-urlencode "chat_id=$CHAT" \
--data-urlencode "text=✅ stage web deployed — ${SHA:0:7} → https://food-market.zat.kz" \
> /dev/null
- name: Notify Telegram on failure
if: failure()
env:
BOT: ${{ secrets.TELEGRAM_BOT_TOKEN }}
CHAT: ${{ secrets.TELEGRAM_CHAT_ID }}
SHA: ${{ github.sha }}
run: |
curl -sS -X POST "https://api.telegram.org/bot$BOT/sendMessage" \
--data-urlencode "chat_id=$CHAT" \
--data-urlencode "text=❌ stage web deploy FAILED — ${SHA:0:7}" \
> /dev/null