A plugin for Sonatype Nexus 1.9.2.x or 2.X which recognizes RPMs in Nexus Maven repositories and generates Yum metadata, so that RedHat-compatible system can use Nexus as software repository.
The Nexus Yum Plugin is for all guys, who are deploying Java application for RedHat-compatible (RHEL, Centos, Fedora) servers and deploy via RPM.
Sonatype Nexus is a common repository manager for Maven, used by many companies to manage their Java artifacts like JAR, WAR, pom.xml files. At ImmobilienScout24 the DevOps-guys started to deploy their configurations and java applications via RPMs and wanted to have a repository manager for their application RPMs. Why don't extend Sonatype Nexus to host RPMs as well?
- Use a Maven repository, hosted in Nexus, containing RPMs as if it is a Yum repository. This leverages the virtual repository mechanism in Nexus which allows you to use Maven tooling to deploy RPMs into a Maven repository but still allow Yum clients to interact with the repository using the protocol it understands.
- Yum repositories are automatically updated if you upload/deploy/delete a new RPM into Nexus.
- Full group support so that you can logically group a set of Yum repositories behind a single URL.
- Have versioned views on repositories:
- You can define aliases for specific versions eg. production=1.2 and testing=2.0 and access them via the alias:
- Create Yum createrepo tasks manually via web interface.
- Multiple createrepo tasks on the same repository get merged.
- Use Yum group repositories as target of staging repositories (Nexus Pro)
- Install Sonatype Nexus
- Download latest nexus-yum-plugin-bundle.zip from our downloads page
- Unzip the bundle to $NEXUS_WORK_DIR/plugin-repository/. The default for $NEXUS_WORK_DIR is ~/sonatype-work/nexus/. For example: unzip nexus-yum-plugin-1.13-bundle-zip -d $NEXUS_WORK_DIR/plugin-repository/
- Install createrepo using your update manager (yum, apt-get, etc.) eg. sudo yum install createrepo
- Make sure that in Nexus Adminstration --> Settings --> Application Server Settings (optional) --> Base URL is set to a vaild URL like : http://your.nexus.domain:8081/nexus
- Sometimes Force Base URL is nessessary, too, see ISSUE 4 . Otherwise the plugin can't determine the server URL and you got RPM locations like null/content/repositories/... in primary.xml.
- Configure Nexus Yum Plugin via yum.xml. See Configuration.
- Restart Nexus. Eg. sudo service nexus stop sudo service nexus start
Now the plugin should be installed.
Here, you'll find everything about configuring Nexus Yum Plugin.
The configuration of the Nexus Yum Plugin can be found in yum.xml in the same directory as nexus.xml : $NEXUS_WORK_DIR/conf/yum.xml Default: ~/sonatype-work/nexus/conf/yum.xml
<?xml version="1.0" encoding="UTF-8"?> <configuration> <!-- timeout for requests for a filtered (versionized) repository --> <repositoryCreationTimeout>150</repositoryCreationTimeout><!-- in seconds --> <!-- enables or disables the creation of a repository of repositories --> <repositoryOfRepositoryVersionsActive>true</repositoryOfRepositoryVersionsActive> <!-- enables or disables of delete rpm events via nexus --> <deleteProcessing>true</deleteProcessing> <!-- delay after which the rebuild of a repository is triggered in which one or more rpms got deleted --> <delayAfterDeletion>10</delayAfterDeletion><!-- in seconds --> <!-- configured aliases --> <aliasMappings> <aliasMapping> <repoId>releases</repoId> <alias>trunk</alias> <version>5.1.15-2</version> </aliasMapping> <aliasMapping> <repoId>releases</repoId> <alias>production</alias> <version>5.1.15-1</version> </aliasMapping> </aliasMappings> </configuration>
to run all tests and create a plugin bundle.