I installed nexus-2.8.0-05-bundle.tar.gz and now I am trying to migrate old (single) repo from Artifactory.
How can I achieve this (Debian7)?
I read about migration plugin but I cannot seem to find the right one... I unzipped nexus-migration-plugin-packaging-1.5-webapp.zip into the nexus installation folder but it doesn't seem to work..or at least I cannot find any related actions from the web admin console localhost:8081/nexus.
Cheers,
newbie
In order to migrate to Nexus you would use the export tool of Artifactory to get the repositories as plain files and folders structure.
Then you create a repo in Nexus and simply copy that storage into place.
Further details are available in the Nexus book migration chapter.
You can also ping us via a support ticket or via the mailings lists or hipchat channel.
PS: The migration plugin is deprecated and should not be used.
Related
Our organization has a locally running instance of Artifactory, and also a local instance of Bitbucket. We are trying to get them to play well together so that Artifactory can serve up our private PHP packages right out of Bitbucket.
Specifically, we'd like to create a Composer Remote Repository in Artifactory that serves up our private PHP packages, where those packages are sourced from git repositories on our local Bitbucket server.
Note that we'd rather not create and upload our own package zip files for each new package version, as suggested here. Ideally, we just want to be able to commit changes to a PHP package in BitBucket, tag those changes as a new package version, and have that new version be automatically picked up and served by Artifactory.
The Artifactory Composer documentation suggests that this is possible:
A Composer remote repository in Artifactory can proxy packagist.org
and other Artifactory Composer repositories for index files, and
version control systems such as GitHub or BitBucket, or local
Composer repositories in other Artifactory instances for binaries.
We've spent a lot of time trying making this work, but haven't been able to do it. The Remote Repository that we create always remains empty, no matter what we do. Can anyone offer an example to help, or even just confirm that what we're attempting isn't possible?
For reference, we've been trying to find the right settings to put into this setup page:
Thanks!
Artifactory won't download and pack the sources for you, it expects to find binary artifacts.
The mention of source control in the documentation refers to downloading the archives from source control systems, either uploaded there as archives (don't do that), or packed by the source control system on download request (that is what you are looking for).
You can use this REST API to download automatically generated zips from BitBucket. If you can configure the composer client to look for the packages in the right place, you're all set.
I'm trying to migrate my artifactory repository to nexus 3, but following sonatype's recommendation, it just shows me how to migrate nexus 2, and from what I've seen, the file system structure is different between versions of nexus.
Has anyone managed this migration yet?
I couldnt find anything in the nexus migration documentation 3.
Here is the link I used from the sonatype site on migration: http://www.sonatype.org/nexus/2015/02/23/migrating-from-artifactory-archiva-or-a-raw-maven-repository-to-sonatype-nexus
Until NXRM3 implements an import ability, the recommended strategy I've heard is to migrate Artifactory to NXRM2 then migrate your NXRM2 to NXRM3.
Depending on what components you use, you may also be able to script the components from Artifactory directly to NXRM3 using stuff like this: http://exchange.sonatype.com/details?extension=4969301365
However, this won't work for all components, like probably won't work for docker. That's not to say you couldn't write something that would work but the linked strategy wouldn't work.
For import, you can watch/vote here. I envision it'll be possible once that's done, however, won't be sure til it's done=)
I am new to Nexus and recently started using nexus and wanted to do some configuration. after successful installation when I run Gradle to upload build artifacts (resultant jar file), it was uploaded successfully but why I cannot see the file at the sonatype-work directory. After going through some tutorials, I came to know that there should be a folder called Storage in sonatype-work directory but it is not there.(FYI, I am using Nexus 3.2).
Please guide me how to cofigure this Storage folder so that I can get those uploaded artifacts directly from the physical path and not from console.
Also please guide me how to publish a complete directory from my local system to Nexus repository manager using Gradle.
In the Nexus 3.x version there's no folder called storage, there's a new area called blob stores(read the official documentation on the sonatype). You can compare screenshots:Nexus 2 and Nexus 3. As you can see, nexus 2 really has this folder (storage, I mean), but nexus 3 has blobs instead storage.
For the uploading(publishing) your build results to the internal Nexus repository, please use gradle-nexus-pluginor the maven-publish plugins.
You can find it on the github, sorry but I can't insert more than two links in the answer :(
First, I know that the upcoming Nexus 3.1 will offer migration of v2 to v3.
I also just applied for the beta migration for v2 to v3 (google forms).
My timing sucks, since the next few days I am going to setup and integrate a new Nexus 3 server.
Is it possible to manually copy my old Maven artifacts (from Nexus v2 server) to this new Nexus v3 server and let Nexus v3 reindex everything?
If so, how?
It's not possible to manually copy, however Nexus Repository Manager 3.1 is now released and you can use it to Upgrade.
As well, the incredible, edible Manfred Moser created this: https://github.com/simpligility/maven-repository-tools/tree/master/maven-repository-provisioner which you can use to take something from a file system into a Maven Repository AKA Nexus Repository Manager. I haven't used it myself, but it's probably exactly what you are looking for.
For those still checking this out, you can also use this simple bash script to import artifacts into Nexus Repository 3: https://gist.github.com/DarthHater/a4f2738e3bd40d242db22633b59dfd63
I have a local installation of Nexus OSS 3.0.0-03.
I am able to upload snapshot and release jars.
Now I want to download those jars via the browser or wget, but I can't seem to find the REST API call to do it (for example in a shell script executed by Jenkins).
Prior to version 3 it seems one could use something like:
http://MY_REPOSITORY/nexus/service/local/artifact/maven/content?r=repoId&g=groupName&a=art&v=LATEST
Any ideas on how to do this with version 3?
If it's latest you are looking for, you can see the answer here: Sonatype Nexus 3 - get latest snapshot
This as of yet does not exist in Nexus Repository 3 but is coming in the nearish future as we revamp the REST API.
However, if you want to download an artifact and know it's coordinates, you can do that via constructing a URL using the patterns here as a helpful tool: https://cwiki.apache.org/confluence/display/MAVEN/Remote+repository+layout#Remoterepositorylayout-Repositoryartifactlayout