0 views collected around this technical thread.
vivo’s CICD artifact management has evolved from manual builds to a comprehensive Platform Management 2.0 that provides unified storage, multi‑type support, version control, promotion, security scanning, lifecycle policies, and fine‑grained access, dramatically reducing errors and operational costs.
This guide walks through installing Jenkins and Nexus via Docker, configuring a Maven hosted repository in Nexus, setting up Jenkins credentials and plugins, and creating a Jenkins pipeline that builds a Maven project and publishes its artifacts to Nexus, enabling automated CI/CD for Java applications.
This guide walks you through installing Jenkins and Nexus via Docker, configuring a Maven hosted repository in Nexus, adding necessary Jenkins plugins and credentials, and creating a Jenkins pipeline that builds a Java project and publishes its artifacts to Nexus, enabling automated CI/CD for your applications.
This article explains what an artifact repository is, compares popular solutions such as Nexus, Harbor, and Docker Registry, and provides step‑by‑step instructions for installing and using a Docker Registry, including common issues and troubleshooting tips for DevOps teams.
The article explains why and how to store external libraries and tools in a private artifact repository, isolate builds from the internet, and verify build stability by testing offline pipelines, emphasizing the importance of managing dependencies for reliable DevOps processes.
This guide walks through installing Jenkins and Nexus Repository Manager with Docker, configuring a Maven hosted repository, adding Nexus credentials and Maven tools in Jenkins, and creating a Jenkins pipeline that builds a Java project and publishes its artifacts to Nexus, illustrating a complete CI/CD workflow.
This guide explains how to store, upload, and retrieve build artifacts using Nexus repository manager through its UI, Maven configuration, Jenkins Nexus Artifact Uploader plugin, custom pipeline functions, and direct REST API calls, including download examples with curl and wget.
Ensuring that all build dependencies—including external libraries, Docker base images, and command‑line utilities—are stored in a controlled artifact repository and testing builds without internet access helps maintain pipeline stability by preventing failures caused by missing or unavailable external resources.
This article introduces JFrog Artifactory, explains its role as a universal artifact repository, outlines its key advantages such as multi‑format support, CI/CD integration, powerful search, lifecycle management, and provides practical guidance on repository naming, permissions, retention policies, and workflow best practices.
This article explains Capital One’s data‑driven approach to creating a single trusted source for all internal software artifacts using JFrog Artifactory, detailing the motivations, implementation steps, release workflow, and the operational benefits achieved.
This guide explains how to deploy Nexus with Docker, define component concepts, configure Maven settings, and use Jenkins pipelines—both script‑based and Nexus plugin—to upload and publish artifacts to Nexus and Artifactory, including API scripts and naming conventions for repository management.
This article shares a DevOps engineer's practical experience of deploying a container‑based build resource pool on OpenShift, managing an artifact repository, and optimizing Jenkins shared libraries with parameterized pipelines to improve CI/CD efficiency and reliability.