From: Raman G. <roc...@gm...> - 2013-08-02 00:41:26
|
I followed the instructions at http://www.jfrog.com/confluence/display/RTF/Upgrading+Artifactory to upgrade my Artifactory 2.7.7 instance to 3.0.2. After the update, my security and other settings have carried over but my repository is completely empty. I didn't see any instructions on the wiki page to export and import the repository, but should I have done that? Is there a way to export the repository from my old MySQL database without installing Artifactory 2.7.7 again? Regards, Raman |
From: Raman G. <roc...@gm...> - 2013-08-02 00:56:26
|
On 08/01/2013 08:41 PM, Raman Gupta wrote: > I followed the instructions at > http://www.jfrog.com/confluence/display/RTF/Upgrading+Artifactory to > upgrade my Artifactory 2.7.7 instance to 3.0.2. > > After the update, my security and other settings have carried over but > my repository is completely empty. > > I didn't see any instructions on the wiki page to export and import > the repository, but should I have done that? Is there a way to export > the repository from my old MySQL database without installing > Artifactory 2.7.7 again? It seems I just needed to wait 10 to 15 minutes... the repository appears to finally be repopulating itself from the export. All is well :) Regards, Raman |
From: Shay B. <sh...@jf...> - 2013-08-04 13:28:48
|
Hi Raman, I guess while you checked your repository, the import process still not completed. You should monitor the logs and wait until the import is done before working against your instance. When the import is completed, you will see the following in artifactory.log: [http-bio-8082-exec-2] [INFO ] (o.a.s.ArtifactoryApplicationContext:475) - ### Full system import finished ### Regards, |
From: vaueff <vol...@1u...> - 2013-08-09 14:37:10
|
Hi, I have the same problem. I tried to upgrade from 2.6.7 to 3.0.2 (professional license). We have several in house repositories with hundreds of GB of artifacts and some cached external repos with a lot of artifacts. The System export did work well, and after the import was finished successfully (some errors occurred, mostly metadata specific) a some in house repositories and the caches of the external repositories have been here but not our two most important repositories for our releases. They are configured, yes but they are completely empty. Before we used a H2 DB and now we wanted to use the default (derby db) Has anyone else this problem? Does anyone know what the problem is? kind regards Volker -- View this message in context: http://forums.jfrog.org/Upgrade-to-Artifactory-3-x-empty-repository-tp7578964p7578987.html Sent from the Artifactory - Users mailing list archive at Nabble.com. |