Skip to content
Define nexus repository structure as code
Branch: develop
Clone or download
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
cmd Add flag to set HTTP request timeout Jan 31, 2019
domain
infrastructure Add default timeout to nexus3 tests Jan 31, 2019
resources removes derived (thus obsolete) information Feb 1, 2019
scripts #3 Adds generic data structure support for Nexus 3 in go, cleans groovy Jan 21, 2019
.editorconfig initial setup Jul 10, 2017
.gitignore initial setup Jul 10, 2017
Jenkinsfile use cloudogu/golang:1.10.2 container for jenkins builds May 15, 2018
Makefile Bump version Jan 31, 2019
README.md Add hint for golang version to use Jan 31, 2019
app.go Finish support for repository type: docker Dec 18, 2018
app_test.go added version to help output Jul 13, 2017
docker-compose.yml Updated error handling, hcl, docker-compose, readme and testing files May 15, 2018
glide.lock Add flag to set HTTP request timeout Jan 31, 2019
glide.yaml Add flag to set HTTP request timeout Jan 31, 2019
pom.xml Add support for repository type: docker Dec 14, 2018

README.md

Nexus Claim

Define your Sonatype Nexus repository structure as code. This script defaults to interact with a nexus server running on localhost.

Development

  • Use golang 1.9 for compiling, 1.10 will lead to a segmentation fault when running the tool!

Syntax of nexus-claim on nexus 3

$ nexus-claim plan -i input.hcl -o output.json
$ nexus-claim apply -i output.json

If in case of doubt, issue nexus-claim --help to get going.

Global Options

--server value, -s value    Url to the nexus server (default: "http://localhost:8081") [$NEXUS_SERVER]
--username value, -u value  Username of a nexus admin user (default: "admin") [$NEXUS_USER]
--password value, -p value  Password of the nexus user (default: "admin123") [$NEXUS_PASSWORD]
--nexus2                    use this flag to use nexus-claim with nexus 2 [$NEXUS_V2]
--help, -h                  show help
--version, -v               print the version

Testing with nexus 3

  1. Have a decent version of Golang installed
  2. Install Golang dependencies with glide install
  3. Build the software in the target/ directory
    • make clean && make
  4. Start up a local nexus
    • docker run -d -p 8081:8081 --name nexus sonatype/nexus3
  5. Plan a custom repository .hcl file
    • target/nexus-claim plan -i resources/nexus3/nexus_custom_example.hcl -o targetState.json
    • this reads existing repositories from the nexus, changes from the given .hcl file will make up the target state as JSON
    • the target state is supposed to be created within the nexus-claim application
  6. Apply target state .json file to nexus
    1. an auto-generated .groovy file responsible for interacting with the nexus API in terms of creating will be uploaded in the nexus.
    2. the .groovy file responsible for creation will be called with the target .json being the argument
  7. The repository changes are being written. Check the nexus frontend for changes.

Things to consider for .hcl of nexus 3

  • on maven2-hosted- and maven2-proxy-repository there must be a maven sector in addition(with versionPolicy and writePolicy)
  • Note the autogenerated .groovy files are only an interaction layer and should not contain larger application logic

Configuration Examples

nexus 3

Examples can be found in the nexus 3 resources directory. Also available in the same directory are resulting target .json files for reference.

nexus 2

Examples can be found in the nexus 2 resources directory

You can’t perform that action at this time.