hetaya.blogg.se - Teamcity youtrack

#TEAMCITY YOUTRACK HOW TO#
#TEAMCITY YOUTRACK UPDATE#
#TEAMCITY YOUTRACK PASSWORD#
#TEAMCITY YOUTRACK DOWNLOAD#

Use the following command, in a PowerShell console: If you have a Build Agent installed on the same server as the TeamCity Service you will also need to stop this. Stopping the TeamCity service may take a few minutes. To stop the TeamCity service, open PowerShell and enter the following command: In order to take a backup of the TeamCity Data Directory, you need exclusive access to the files, so you need to shut down the TeamCity Services.

#TEAMCITY YOUTRACK DOWNLOAD#

Once the backup has completed, TeamCity will display a summary and show the path of the backup which is also a hyperlink that you can click to download the file: – the backup process can take a number of minutes: Depending on the number of build configurations, amount of historical data etc.

#TEAMCITY YOUTRACK UPDATE#

The screen will update to show you the backup process. I've highlighted the UI which shows you where the backup will end up. Once you are in the backup screen you can select which items you want to select. To access the backup screen you will need navigate to the Administration screen (assuming you are a TC Administrator) and then select the "Backup" option from the secondary navigation. The second, and easier mechanism is to use the TeamCity Admin UI. sh file and is quite simple to use, if you want to back up everything (configuration, database, build logs, personal changes) you would run it using the following switches:īy default the backup will be created in the \backup directory with the following file name: TeamCity_Backup_.zip, where the timestamp is in the YYYYMMDD_HHMMSS format. The tool can be found in \bin directory and exists in the form of a. There are two main mechanisms for backing up the TeamCity database the first is using the maintainDB tool – this gives you command line control of the back up process. To perform a migration you need to backup (and restore) both of these data repositories. In order to perform a migration, you first need to understand how TeamCity is architected, especially how TeamCity stores its data in two separate repositories the Data Directory for server settings, build artefacts, logs & configuration, based on the file system and a second, containing build information, configuration & statistics which is stored in a database (HSQLDB, Microsoft SQL Server, MYSQL, PostgreSQL, Oracle).

#TEAMCITY YOUTRACK HOW TO#

This step by step guide is going to cover how to migrate to a new Windows Server instance running Microsoft SQL Server. Luckily, due to the way that TeamCity has been designed, all of these scenarios are supported. If you've been using TeamCity for a number of years, there will come a time where the server it's running on will reach its end of life and your TeamCity instance will need to be moved to a fresh server.Īs part of this migration process, you may decide to change OS from Linux to Windows or persistence mechanism from the internal HQL data store, or an Oracle Database to SQL Server or MySQL.

#TEAMCITY YOUTRACK PASSWORD#

The password will be displayed in the parameter list.By Howard van Rooijen Co-Founder 30th July 2013.

On the Edit Parameter window click the Save button.

Set the type to Text and click the Save button.

To display the value of the password in the TeamCity UI again

To use the parameter in a build step, surround it with % signs.ĭisplay the obfuscated password in the TeamCity UI.

Click the Save button on this window and the on the parent window to save the parameter.

Set the Display to Hidden, and the Type to Password to hide the value from the user interface.

Enter the name of the parameter, the password value, and click the Edit button to set the special settings,.

On the project page open the Parameters page,.

In the TeamCity web interface navigate to the project,.

When a TeamCity build step needs to use a password, there is a way to obfuscate it. Obfuscate the password in the TeamCity UI