Artifactory
Role in the Platform
Artifactory stores approved build artifacts used by WxCIP automation. The old documentation identifies wxcip-automation-tools-docker for selected container images and wxcip-automation-tools-generic-generic for versioned automation bundles.
Exporter images normally use ECR in the Webex Kubed delivery path. Selected SVS-UC-Ansible and automation artifacts use Artifactory. Confirm the owning pipeline before assuming an artifact should be published to both registries.
Artifact Flow
graph LR
Git["Source Commit"] --> Harness["Harness Pipeline"]
Harness --> ECR["ECR: Kubed Images"]
Harness --> Art["Artifactory: Approved Images / Bundles"]
ECR --> Kubed["Webex Kubed"]
Art --> AWX["AWX / Automation Consumers"]Operational Standards
- Publish through an approved pipeline, not from a personal workstation.
- Use traceable, immutable versions tied to a source commit.
- Retain checksums, build metadata, and scan evidence.
- Restrict write access and use SSO or managed service credentials.
- Do not overwrite a released artifact with different content.
- Verify consumers before applying retention or cleanup policies.
Troubleshooting
| Symptom | Check |
|---|---|
| Artifact missing | Pipeline destination, repository name, and publish stage |
| Authentication failure | SSO/service identity, token expiry, and repository permission |
| Consumer receives 404 | Exact path, case, version, and virtual-repository mapping |
| Digest mismatch | Source build, republished tag, and proxy/cache path |
| AWX still uses older bundle | Project sync/version reference and execution-environment cache |