Snapshot:It’s intended to be used for code snapshot version and must have the -SNAPSHOT suffix in pom description.Every upload overwrite the previuos artifact. Releases:It’s intended to be used for release candidates and must not have the -SNAPSHOT suffix in pom description.So, once put the name for the repository, it’s important to understand what is Version Policy meaning. Once selected maven2 (hosted) recipe, we are able to create the repository. The button create repository makes a new repository. To complete the first step, we need to log as administrator (default admin’s password is “admin”) and go to the upper tab Server administration and configuration and select the left menu Repositories. Create a user in order to get the access to the Jenkins pipeline.Create a new repository where stores our artifacts.Open your browser at and you’ll see the Nexus OSS Dashboard! Once downloade the package and extract it to any folder, it’s time to run the application You can also install and run Nexus OSS as a service on you OS, anyway running as stand alone achieves my purpose for this article.
Anyway, it’s available for multiple platforms and environments. I installed the open source version as Windows stand alone application.
Let’s start to see how configure Nexus OSS to store my artifacts. If you’re asking yourself why I should do such thing or why it should concerned my delivery processing, please read the Foreword on the first part of the serie. Likewise the first part of this serie ( When Jenkins meets an Artifact Repository – JFrog and Nexus OSS), I installed the Artifact Repository on my local OS (btw Windows) and built a Jenkins pipeline in order to upload my artifact after building maven package. Continuing from the first part of this journey through the Artifact Repository, I’m going to develop a Jenkins pipeline to Upload an artifact to Nexus OSS in a Continuous Delivery/Deployment process.
0 kommentar(er)
