Apa iku manajemen artifact ing CI/CD?

Question

Accepted Answer

**Artifacts** yaiku asil saka proses build (compiled binaries, packages, Docker images) sing dideploy. **Manajemen artifact** — nyimpen, versioning, lan promote artifacts iki liwat registry/repository — penting kanggo deployment sing reliable lan traceable.

## Apa kuwi artifacts

```text
The BUILD produces ARTIFACTS — the deployable outputs:
  → Docker IMAGES, compiled binaries, JARs/WARs, npm packages, zip bundles, etc.
→ These are what actually get DEPLOYED (not the source code directly).
```

## Artifact repositories/registries

```text
Artifacts are stored in REPOSITORIES/REGISTRIES (versioned, central storage):
  → Container registries: Docker Hub, AWS ECR, GitHub/GitLab Container Registry
  → Package repositories: npm registry, Maven, PyPI, Artifactory, Nexus
→ The pipeline BUILDS an artifact, PUSHES it to the registry, and DEPLOYS from there.
```

## Prinsip kunci: build sekali, deploy ing jaba mana wae

```text
Build the artifact ONCE, then promote the SAME artifact through environments:
  build → artifact v1.2.3 → deploy to STAGING → (tested) → deploy SAME v1.2.3 to PROD
  ✓ what you TESTED in staging is EXACTLY what you deploy to production (no rebuild)
  ✗ rebuilding per environment risks differences (different deps, build env) → bugs
→ Versioned, immutable artifacts ensure consistency and traceability.
```

## Benefits lan practices

```text
✓ VERSIONING — each artifact tagged with a version → know exactly what's deployed
✓ TRACEABILITY — trace a deployed artifact back to its commit/build
✓ ROLLBACK — redeploy a previous artifact version easily
✓ IMMUTABILITY — artifacts don't change once built (consistent, reproducible)
✓ Retention/cleanup policies; scan artifacts for vulnerabilities
```

## Ngapa iki penting

Ngerteni manajemen artifact iku berharga amarga **artifacts yaiku sing bener-bener dideploy**, lan manajemene kanthi apik iku penting kanggo deployment sing reliable, traceable, lan konsisten, dadi ilmu CI/CD sing gunane. **Artifacts** (asil deployable saka build — Docker images, binaries, packages) yaiku sing dideploy (dudu source code langsung), lan nyimpenake ing **versioned registries/repositories** (container registries, package repositories) yaiku carane pipeline manajeme: build artifact, push menyang registry, lan deploy saka kana.

**Prinsip kunci — build sekali, deploy ing jaba mana wae** — utamane penting: build artifact **sekali** lan promote **artifact sing sama** liwat environments (staging banjur production) njamin **apa sing wis ditest yaiku persis apa sing dideploy** (ora ana per-environment rebuilds sing bisa ngenalake bedane saka dependencies sing beda-beda utawa build environments, nyebabake bugs) — praktik fundamental kanggo deployment sing reliable lan konsisten sing nyegah "iku berjaya ing staging" kelas masalah sing disebabake dening rebuild.

Ngerteni **benefits** — **versioning** (ngerti persis apa sing dideploy), **traceability** (trace deployed artifact bali menyang commite lan builde, bernilai kanggo debugging lan auditing), **easy rollback** (redeploy artifact version sadurunge), lan **immutability** (artifacts ora owah biyen build, njamin reproducibility), tambah practices kaya vulnerability scanning — ngrefleksikake carane artifact management sing bener-bener suportna reliable operations.

Samarga artifacts yaiku deployed units sing bener-bener lan manajemene kanthi apik (versioning, prinsip build-once-deploy-everywhere, traceability, immutability) penting kanggo deployment sing konsisten, traceable, lan reliable, lan amarga ngerteni artifacts, registries, lan utamane prinsip build-once iku bernilai kanggo sound delivery, ngerteni manajemen artifact iku bernilai, practically-relevant CI/CD knowledge — bagean penting saka reliable delivery sing njamin konsistensi antarane apa sing diteset lan dideploy, mungkasi traceability lan rollback, lan ngrefleksikake mature deployment practices.