Switch CI to new Gitea registry; drop Portainer trigger

This commit is contained in:
2026-05-03 15:44:58 +00:00
parent d0e8503e13
commit ec2cf5f3b9
2 changed files with 3 additions and 7 deletions
+2 -6
View File
@@ -52,7 +52,7 @@ jobs:
- name: Login to Gitea Registry - name: Login to Gitea Registry
uses: docker/login-action@v3 uses: docker/login-action@v3
with: with:
registry: git.dev.microservices.al registry: git.dev.trmtracking.org
username: ${{ secrets.REGISTRY_USERNAME }} username: ${{ secrets.REGISTRY_USERNAME }}
password: ${{ secrets.REGISTRY_PASSWORD }} password: ${{ secrets.REGISTRY_PASSWORD }}
@@ -61,8 +61,4 @@ jobs:
with: with:
context: . context: .
push: true push: true
tags: git.dev.microservices.al/trm/tcp-ingestion:main tags: git.dev.trmtracking.org/trm/tcp-ingestion:main
- name: Trigger Portainer Deploy
if: success()
run: curl -X POST "${{ secrets.PORTAINER_WEBHOOK_URL }}"
+1 -1
View File
@@ -6,7 +6,7 @@
# Redis. # Redis.
# #
# For STAGE and PRODUCTION deployment, use the multi-service compose in # For STAGE and PRODUCTION deployment, use the multi-service compose in
# the sibling `deploy/` repo (https://git.dev.microservices.al/trm/deploy), # the sibling `deploy/` repo (https://git.dev.trmtracking.org/trm/deploy),
# which references this service by its registry image tag instead of # which references this service by its registry image tag instead of
# building locally. # building locally.
# #