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 Integration was only introduced in Artifactory 2.1.3 you cannot loose this information :)
Yoav On Tue, Apr 27, 2010 at 9:59 PM, Bruno Medeiros <[email protected]> wrote: > >> *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 mean? I just did a system export with "Create .m2 >> compatible export" check. Is it supposed to work? >> > > I did a full system export with .m2 compatible layout in my 2.0.1 > installation and a full system import on my 2.2.3 fresh install and all > seems to be ok. > > I don't know what is the "Build information" mentioned in the warning, but > all seems to be right here. > > I didn't metion in the first post, but I'm migrating from one host to > another, so I decided to do a filesystem-mysql setup instead of a pure blob > mysql setup, witch seems to be more safe an recommended. > > Thanks, Yoav! > > -- > BrunoJCM > > > ------------------------------------------------------------------------------ > > _______________________________________________ > Artifactory-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/artifactory-users > >
------------------------------------------------------------------------------
_______________________________________________ Artifactory-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/artifactory-users
