Build and push multi-platform Docker images to Google Artifact Registry. Use when user asks to build, push, or deploy a Docker image with a tag. Triggers: "build and push", "push docker image", "build with tag", "deploy image".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.
Build and push multi-platform Docker images to the melosys-api Google Artifact Registry.
This repo-local skill intentionally overrides the global
docker-build-push, which auto-detects the image name from the cwd (basenameof the git root) and would mis-name images in parallel checkouts likemelosys-api-claude.
melosys-apiThe image repository is always melosys-api, never the cwd directory name.
Parallel workspaces may be checked out as melosys-api-claude, melosys-api-2,
etc., but the published image name never changes.
europe-north1-docker.pkg.dev/nais-management-233d/teammelosys/melosys-api
docker buildx build --platform linux/amd64,linux/arm64 \
-t europe-north1-docker.pkg.dev/nais-management-233d/teammelosys/melosys-api:TAG \
--push .
Replace TAG with user-specified tag.
The Dockerfile is single-stage (distroless) and copies a pre-built JAR
(COPY /app/target/melosys-sb-execution.jar) — it does NOT build the JAR
itself. So you must produce the JAR before the buildx build whenever code
changed or app/target/ has no current JAR.
make build-fast (mvn clean install -DskipTests)--push — keep the image path exactly as shown above-t argument ends with /melosys-api:TAG
(not /melosys-api-claude:TAG or any other variant)docker buildx create --name multiplatform --use --driver docker-container || docker buildx use multiplatform
Message: "Reauthentication failed"
Solution: Ask user to run gcloud auth login, then retry
Cause: Image built only for arm64
Solution: Use --platform linux/amd64,linux/arm64 flag
After successful push:
Done!
Image details:
- Tag: europe-north1-docker.pkg.dev/.../melosys-api:TAG
- Platforms: linux/amd64, linux/arm64
- Manifest digest: sha256:...
아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.
로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.
아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.
Expert knowledge of Altinn A1 application processing for posted workers in melosys-api. Use when: (1) Understanding Altinn søknad/skjema processing, (2) Debugging MedlemskapArbeidEOS form mapping, (3) Understanding SoeknadMapper transformations, (4) Investigating posted worker application issues, (5) Understanding the MOTTAK_SOKNAD_ALTINN saga flow.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Expert knowledge of Employer/Employment integration (EREG/AAREG) in melosys-api. Use when: (1) Working with organization data from EREG (Enhetsregisteret), (2) Working with employment data from AAREG (Arbeidsforhold), (3) Understanding employer/organization lookup, (4) Debugging employer or employment issues, (5) Understanding the mapping between register data and domain models. Triggers: orgnummer, arbeidsforhold, EREG, AAREG, Enhetsregisteret, registeropplysninger, ansettelsesperiode, saksopplysning.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Modular monolith architecture overview for melosys-api. Use when needing to understand module structure, dependencies between modules, where to place new code, or when changes in one module might affect others. Triggers: "architecture", "module dependencies", "where should I put", "which modules", "dependency graph".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Expert knowledge of Behandling (case treatment) domain in melosys-api. Use when: (1) Understanding the behandling lifecycle and status transitions, (2) Debugging issues with behandling creation, status changes, or closure, (3) Understanding relationships between Fagsak, Behandling, and Behandlingsresultat, (4) Investigating why a behandling is stuck or has wrong status, (5) Understanding Behandlingstyper, Behandlingstema, Behandlingsstatus enums, (6) Debugging journalføring or SED-triggered behandling creation, (7) Understanding behandling creation via saksflyt sagas.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Expert knowledge of Behandlingsresultat (treatment result) domain in melosys-api. Use when: (1) Understanding result types and their meaning (FASTSATT_LOVVALGSLAND, MEDLEM_I_FOLKETRYGDEN, etc.), (2) Working with periods - Lovvalgsperiode, Medlemskapsperiode, Anmodningsperiode, Utpekingsperiode, (3) Debugging vedtak/decision metadata, criteria evaluation, or social insurance charges, (4) Understanding EU/EEA coordination logic and Article 16 exception handling, (5) Working with trygdeavgift (social insurance charge) calculations.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Expert knowledge of Brev (letter generation) in melosys-api. Use when: (1) Producing letters and decision documents (vedtaksbrev), (2) Understanding Dokgen templates and mapping, (3) Configuring letter recipients and distribution, (4) Debugging letter generation issues, (5) Adding new letter types or templates.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.