Artifact Promotion
325 incident problems about Artifact Promotion. Start with the reviewed ones.
먼저 읽을 가이드
추천 문제
All problems (325)
CICD-1430A remote buildx cluster stays nominal and reproducibility checks failA remote buildx cluster stays nominal and reproducibility checks fail focuses on Artifact Promotion and asks the reader to isolate the key signal in docker. Strict reproducibility can be broken by tar implementation differences...CI/CDAdvanced15 minProCICD-1450A remote buildx farm stays healthy and reproducibility checks failStrict reproducibility fails only on builds scheduled to one recently patched worker.CI/CDAdvanced15 minProCICD-1384An Argo CD sync reaches Healthy and traffic still serves the old imageA GitOps rollout appears healthy and later the cluster keeps serving the previous image despite visible commit history showing an update.CI/CDAdvanced15 minProCICD-1309Artifact downloads succeed on Linux and fail on WindowsA matrix build publishes shared outputs and only Windows package jobs start breaking after a naming cleanup.CI/CDAdvanced15 minProCICD-1348A Buildx bake release looks complete and one architecture tag later disappearsA Buildx bake release looks complete and one architecture tag later disappears focuses on Artifact Promotion and asks the reader to isolate the key signal in docker. Successful per-arch builds do not guarantee the final multiarch ta...CI/CDAdvanced16 minProCICD-1316A buildx cache exporter looks healthy and still slows every runA team adds release metadata injection and later loses all BuildKit cache reuse without changing the Dockerfile stages.CI/CDAdvanced16 minProCICD-1328A Buildx multiarch pipeline publishes a manifest list and one architecture is...A Buildx multiarch pipeline publishes a manifest list and one architecture... focuses on Artifact Promotion and asks the reader to isolate the key signal in docker. A present manifest list does not prove every referenced architecture...CI/CDAdvanced16 minProCICD-1297A nested package publish with OIDC fails only in the monorepo release jobA monorepo package publishes fine locally and later fails only in the centralized CI release workflow.CI/CDAdvanced16 minProCICD-1304A remote state lock looks cleared in DynamoDB but the next plan still refuses to runAn interrupted deployment unblocks the lock table but later runs still refuse to proceed with a lock-style error.CI/CDAdvanced16 minProSECURITY-1257A secret is rotated but alerts keep firingA team revokes a credential and still sees recurring detections tied to the same historical leak window.SecurityIntermediate16 minProCICD-1308A speculative Terraform plan in VCS succeeds but the real apply failsA team trusts green speculative plans and later finds applies failing only when merged through the VCS trigger path.CI/CDAdvanced16 minProCICD-1303Terraform init succeeds but apply failsA team refactors shared credentials logic and later only apply fails while init and state refresh continue to work.CI/CDAdvanced16 minProCICD-1273A cache hit restores successfully but the next job failsA matrix build spanning x64 and arm64 starts showing nondeterministic failures after cache keys were simplified.CI/CDAdvanced17 minProCICD-1285A matrix release publishes the right artifacts but the production deploy reuses staging metadataA signed release pipeline shows matching artifacts and later production deploys an older or partially updated manifest.CI/CDAdvanced17 minProCICD-1299A multi-arch image promotion succeeds but arm64 pods fail laterA team adds multi-arch release support and later one architecture alone begins failing cluster admission.CI/CDAdvanced17 minProCICD-1263A private submodule checkout worked before repository hardening but now failsCI/CD incident scenario used for structured troubleshooting practice.CI/CDAdvanced17 minProCICD-1268A private submodule checkout worked before repository hardening but now failsA security hardening change reduces token permissions and suddenly only private submodule checkout begins failing in CI.CI/CDAdvanced17 minProSECURITY-1232A revoked credential still keeps surfacing in alertsAfter a credential rotation, scanners continue to alert because an old downloadable debug archive still contains generated metadata from the leak window.SecurityIntermediate17 minProSECURITY-1227A revoked token keeps triggering alertsSecret rotation is complete and scanners still report findings tied to historic debug bundles or retained CI artifacts.SecurityIntermediate17 minProSECURITY-1252A rotated secret keeps alertingAfter incident response, teams still see alerts tied to an older downloadable diagnostic bundle produced during the leak window.SecurityIntermediate17 minPro