https://github.com/sonatype-nexus-community/nexus-repository-import-scripts

A few scripts for importing artifacts into Nexus Repository
https://github.com/sonatype-nexus-community/nexus-repository-import-scripts

bash maven nexus-extension nexus-repository npm nuget

Last synced: 21 days ago
JSON representation

A few scripts for importing artifacts into Nexus Repository

• Host: GitHub
• URL: https://github.com/sonatype-nexus-community/nexus-repository-import-scripts
• Owner: sonatype-nexus-community
• License: apache-2.0
• Created: 2017-03-24T17:23:58.000Z (over 7 years ago)
• Default Branch: master
• Last Pushed: 2023-06-15T02:13:53.000Z (about 1 year ago)
• Last Synced: 2024-02-23T10:34:23.098Z (4 months ago)
• Topics: bash, maven, nexus-extension, nexus-repository, npm, nuget
• Language: Shell
• Size: 9.77 KB
• Stars: 179
• Watchers: 19
• Forks: 92
• Open Issues: 9
• Metadata Files:
  • Readme: README.md
  • License: LICENSE

Lists

• awesome-stars - nexus-repository-import-scripts - nexus-community | 193 | (Shell)

README

        
# Nexus Repository Import Scripts

## Wut?

These are bare bones bash scripts to import a Nexus 2 Maven, NuGet or npm repository (and likely other file system based repos)

into Nexus Repository 3.

### Wut does it do?

Imports artifacts into a Nexus Repository 3 Maven2, NuGet or npm hosted repo.

### Wut does it not do?

Literally anything else. You want security? Better set it up yourself.

## How do I use it?

* Maven

  * cd rootdirectorywithallyourartifacts

  * ./mavenimport.sh -u admin -p admin123 -r http://localhost:8084/repository/maven-releases/

  * Watch a bunch of verbose output from curl

  * If need be, change -u to user, -p to password, and -r (I bet you'll have to change this) to the repo you want to upload in to

* NuGet

  * cd rootdirectorywithallyournugetpackages

  * ./nugetimport.sh -k APIKEYFROMNEXUS - r http://localhost:8084/repository/nuget-hosted/

  * Watch the money roll in and the haters start askin

  * You'll need to obtain your APIKEY for Nexus Repository, and obviously set -r to the repo path you want to use

* npm

  * npm login --registry http://localhost:8084/repository/npm-internal/

  * cd rootdirectorythatcontainsallnpmmadness

  * ./npmimport.sh -r http://localhost:8084/repository/npm-internal/

  * Watch a bunch of stuff prolly fail because it has extra build steps, figure those out and then remediate if you really care

  * Set -r and --registry to the NPM hosted repo you plan to use

## Like it?

Great, buy me a beer.