CI/CD मा artifact management के हो?

Question

Accepted Answer

**Artifacts** भनेको build process को output (compiled binaries, packages, Docker images) हो जसलाई deploy गरिन्छ। **Artifact management** — यी artifacts लाई store, version, र registry/repository मार्फत promote गरिने — विश्वसनीय र traceable deployments को लागि महत्त्वपूर्ण छ।

## 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.
```

## मुख्य सिद्धान्त: एकपटक build गर, सबै ठाउँमा deploy गर

```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.
```

## फाइदा र 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
```

## यो किन महत्त्वपूर्ण छ

Artifact management बुझ्नु मूल्यवान छ किनभने **artifacts नै वास्तविक रूपमा deploy गरिन्छ**, र तिनीलाई राम्रोसँग manage गर्नु विश्वसनीय, traceable, consistent deployments को लागि महत्त्वपूर्ण छ, त्यसैले यो उपयोगी CI/CD ज्ञान हो। **Artifacts** (build को deployable outputs — Docker images, binaries, packages) नै deploy गरिन्छ (source code सीधै होइन), र तिनीलाई **versioned registries/repositories** मा (container registries, package repositories) store गर्नु pipeline ले तिनीलाई कसरी manage गर्छ भन्ने बुझाउँछ: artifact build गर्नु, यसलाई registry मा push गर्नु, र त्यहाँबाट deploy गर्नु।

**मुख्य सिद्धान्त — एकपटक build गर, सबै ठाउँमा deploy गर** — विशेष गरी महत्त्वपूर्ण छ: artifact **एकपटक** build गर्नु र त्यही **एउटै artifact** लाई environments (staging त्यसपछी production) मार्फत promote गर्नु सुनिश्चित गर्छ कि **तपाईंले test गरेको कुरा नै तपाईंले deploy गर्दै हुनुहुन्छ** (कुनै पनि per-environment rebuilds छैन जसले निर्भरताहरु वा build environments को भिन्नताबाट फरकहरु आनसक्ते छन्, बग को कारण हुन सक्छ) — विश्वसनीय, consistent deployments को लागि एक मौलिक practice जो