*Preserving Build Information*
*Please also note that using the upgrade process is the only way to move
deployed build-information forward. You cannot import an export of 2.1.x
with BuildInfo data into 2.2.x. This is a result of a bug that has already
been resolved.*
What does it exactly
Glad you managed, and yes - mysql/fs is a better option overall.
The caveat about the build information old migration bug refers to migration
of metadata about builds stored in Artifactory by our CI Build Integration (
http://wiki.jfrog.org/confluence/display/RTF/Build+Integration).
Since Build
On Tue, Apr 27, 2010 at 17:33, Yoav Landman yo...@jfrog.org wrote:
Glad you managed, and yes - mysql/fs is a better option overall.
Hi again, Yoav.
As I changed the subject, let me explain again what I'm doing here. I'm
trying export the whole 2.0.1 system and import in a 2.2.3 fresh install.
Just adding some more info:
I did a new export with artifactory especifc metadata, and then a import on
the new server. This new import didn't show the No metadata files found
warning.
But when ask for the maven-metadata.xml, a wrong file is given (and
different from the file that are supposed
