I am a teamcity developer and our organisation currently uses Team-city 9.0.3 Free version. Now we maxed out Builds. So we are planning to take an enterprise edition.
But before that we need to upgrade the teamcity to latest version 10.x. while i am doing the upgrade it throws the following error.
Please click the link to see the error
The steps i did for the upgrade are
-- Take a back up of entire Teamcity which will be in /root/.BuildServer/backup
-- Stop the Teamcity server and delete the whole teamcity directory
-- copy the backup .Zip file into import section.
-- download the latest teamcity and do the necessary configurations and start the teamcity server.
-- go to Administration/Import and start importing the file from /root/.BuildServer/import
While importing i am getting the above error as version is not supported.
Please help me on this so that i have to upgrade the Teamcity and go for enterprise edition
Thankyou in advance..
It sounds like you are trying to import a backup created with TeamCity 9 into TeamCity 10, that isn't supported, backups can only be restored with the same version they were created with.
When you install TeamCity you usually have a data directory (probably ".BuildServer" in your case) and the software in a different location. You shouldn't delete the data directory, you should upgrade the database and data directory in place (TeamCity will prompt to do this when the new software starts, refer maintenance mode below).
If you continue with your proposed route you'll need to create a fresh TeamCity 10 database with the new schema version, however you'll loose all the other settings and data as that backup sounds like a project config only backup.
JetBrains provide detailed guides to perform upgrades:
https://confluence.jetbrains.com/display/TCD10/Upgrade
https://confluence.jetbrains.com/display/TCD10/TeamCity+Maintenance+Mode
Related
I have a Windows Server 2012 with an active repository on VisualSVN version 3.3.1.
We want to copy this to a new VisualSVN Server instance version 5.1.0 on a Windows Server 2019 and replace the old server.
Is there a way to duplicate the repository completely and with all permissions etc. and import it on the other server?
We have already done it with the commands
svnadmin dump REPOS_PATH [-r LOWER[:UPPER]] [--incremental] [--deltas]
and
svnadmin load REPOS_PATH [-r LOWER[:UPPER]].
However, it does not retain the permissions and locks here.
Also, I found a post saying to only copy the files in the repository directory but I am not sure whether this is the right and correct way: Post
Migrating VisualSVN Server
You don't need to use svnadmin dump and svnadmin load when migrating VisualSVN Server onto a new server computer.
You should not mix up the server migration and upgrade tasks. They have to be approached separately if you plan to migrate the server and all repositories from one computer to another. Normally, you need to either to upgrade your existing server installation to the latest version and then upgrade, or upgrade you existing server installation and upgrade later.
Migration instructions are given in the article KB166: Migrating VisualSVN Server to another computer.
Upgrade instructions are given in the article KB204: Upgrading to VisualSVN Server 5.1.
Migrating a repository
You don't need to use svnadmin dump and svnadmin load when importing only one or a few repositories onto another VisualSVN Server installation.
If your task is to migrate the server with all the repositories, see the section above.
When you want to import an individual repository from another server installation (without needing to migrate the server itself and all other repositories), you need to follow the instructions from the article KB10: Importing Repositories into VisualSVN Server:
Create a backup of the repository and restore it on the new computer.
or
Copy the directory of the individual repository onto a new computer and import it.
Repository settings including user permissions and hook scripts will be retained with both approaches.
I have a Xamarin project that builds just fine on my local machine but is not building on the azure server. Anyone see this before ?
##[error]The nuget command failed with exit code(1) and error(NU1201: Project XXX.XXXX.XXXXX is not compatible with monoandroid10.0 (MonoAndroid,Version=v10.0). Project XXX.XXXX.XXXXX supports: netstandard2.1 (.NETStandard,Version=v2.1)
Upgrade your nuget version to 5.8 and this will all go away :)
If you use Azure pipelines to Build and deploy Xamarin apps, please refer to this doc. And if you use Microsoft-hosted agent, its build environment is different from local machine, such as it may lack of some software or installs different software version. You can see the installed software for each hosted agent by choosing the Included Software link in the table.
To your issue, please check which NuGet version do you use to build this project locally, and then use the NuGet Tool Installer task in Azure pipeline to specify this NuGet version(maybe 5.8.0 works for your issue as Mouse commented) to build your project with Microsoft-hosted agent.
Also you could deploy local self-hosted Windows agent and use it in Azure pipeline to build your project, which will run local build environment.
BTW, you could refer to this doc: Review logs to diagnose pipeline issues to make initial troubleshooting steps when encounter pipeline issues.
We are planning to migrate from Sonarqube 5.6 version to Sonarqube 7.3 developer edition.
Because of huge lines of code we are planning to migrate specific project to Developer edition to regulate cost Hence Is there any way in to migrate only specific project not all the projects from current instance to Developer edition?
There is no out of the box way to do migrate a specific project: on startup of SonarQube the whole database is migrated in place. The commercial Sonar DB Copy Tool is copying table by table and also not based on a project. That is why it is so very important to make a database backup before you start migrating for the case something goes wrong (no rollback mechanism available). To prevent the migration of some large projects you can remove them before you upgrade and start the migration. See also the migration path documentation. The migration path you have to follow is: 5.x => 5.6.7 LTS => 6.7.x LTS => 7.x. Starting with an empty database can also be a consideration.
I want to upgrade SonarQube and I haven't done this before so I have few question. Please could you help me with them?
How can I find which edition is installed on my server?
How can I find if the installed version is licensed or not?
How can I upgrade from 5.6.4 to 6.7 LTS? Do you have upgrade guide for the same?
You can always find which version is installed by logging into the SonarQube web app and looking at the footer of the page or by going to Administration / System / System Info. If you for some reason can't log in to the web app, and installation folder name does not contain the version number as it does by default, look in the "lib" folder for a file that looks like "sonar-application-6.3.1.jar". That will tell you the version number as well.
Here are the general steps for upgrading, from the Upgrade the Server docs:
Download and unzip the SonarQube distribution of your edition in a
fresh directory, let's say $NEW_SONARQUBE_HOME
Manually install the
non-default plugins that are compatible with your version of
SonarQube. Use the Compatibility Matrix to ensure that the versions
you install are compatible with your server version. Note that the
most recent versions of all SonarSource code analyzers available in
your edition are installed by default. Simply copying plugins from
the old server to the new is not recommended; incompatible or
duplicate plugins could cause startup errors.
Update the contents of
sonar.properties and wrapper.conf files (in
$NEW_SONARQUBE_HOME/conf) with the settings of the related files in
the $OLD_SONARQUBE_HOME/conf directory (web server URL, database,
ldap settings, etc.). Do not copy-paste the old files. If you are
using the Oracle DB, copy its JDBC driver into
$NEW_SONARQUBE_HOME/extensions/jdbc-driver/oracle
Stop your old
SonarQube Server
Start your new SonarQube Server
Browse to
http://yourSonarQubeServerURL/setup and follow the setup
instructions
Analyze your projects (and compute your
Views|Portofolios|Application if you own the Enterprise Edition
product) to get fresh data
Before embarking on this, you will want to check out the intermediate upgrade notes for each version in order: 6.0, 6.1, 6.2, 6.3, 6.4, 6.5, 6.6, and 6.7.
Note that upgrade notes for versions after 6.7 are hosted at the new documentation site.
I'm currently using TeamCity 9.0 with MS-SQL as the repository. I want to upgrade to version 9.1.1. I run the installer and I see 9.0 being uninstalled, followed by the 9.1.1 installation. After the installation is done TeamCity won't come back. The Web portal shows this error:
TeamCity server is connecting to MSSQL database. The database server is not started yet, or the database specified in '/config/database.properties' file is inaccessible.
I am using the same user account as the previous installation so it doesn't look like a permissions issue.
According to the documentation the installer should prompt for the data directory, but I never got that prompt.
While uninstalling I removed the TeamCity/lib/jdbc folder (those are the libraries to use MS-SQL). After installing 9.1.1 I copied back the folder and restarted the TC service.
Thoughts?
Check your config/database.properties file, and see if your database is still there.