The following data is not included into backup:īuild artifacts (because of their size). Īdditionally, it is important to keep in mind that there is some data not included in TeamCity backups. Please see our documentation here for additional information on this process.
#TEAMCITY SERVER FULL#
Yes, you can use a full backup to help with your migration in this way. I saw that my existing users will be dropped when I make the switch will my role and group structures be dropped as well or will they be preserved (i.e., will I still have "Role A" or "Group 3" with existing permissions intact but without users assigned to them)? I also have one additional question: I am currently using the built-in Teamcity authentication, but I would like to switch to authenticating via Active Directory. In case it's important, my current data root is the default $HOME/.BuildServer and the Teamcity server is installed in $HOME/tomcat/webapps on the new machine it will be /opt/teamcity/BuildServer and /opt/teamcity/tomcat. war distribution deployed to Tomcat rather than the. BuildServer directory on the old machine to my $TEAMCITY_DATA_ROOT directory on the new server so that they are identical (including the artifacts, etc.), set up the Teamcity.war in the new Tomcat, and then fire up the new server? I typically use the. My question is, rather than using maintainDB to get some of the other backup information to move over, can I simply shutdown the old instance, rsync the. I'm already using an external MySQL database, so connecting the new machine to the DB once the old Teamcity instance is shut down will be simple.
I'd like to move my Teamcity server to a new machine, going from one Linux box to another.
0 kommentar(er)
