{"id":12715,"date":"2018-09-06T16:59:55","date_gmt":"2018-09-06T16:59:55","guid":{"rendered":"https:\/\/blog.jetbrains.com\/teamcity\/?p=6725"},"modified":"2018-09-06T16:59:55","modified_gmt":"2018-09-06T16:59:55","slug":"teamcity-on-azure-marketplace","status":"publish","type":"teamcity","link":"https:\/\/blog.jetbrains.com\/fr\/teamcity\/2018\/09\/teamcity-on-azure-marketplace","title":{"rendered":"TeamCity on Azure Marketplace"},"content":{"rendered":"

Some time ago we announced TeamCity Azure Resource Manager <\/a>for TeamCity deployment in Azure cloud. Now we’re glad to provide the TeamCity offer<\/a> in the Azure Marketplace for streamlined TeamCity setup.<\/p>\n

It is also available as a TeamCity<\/a> download option on the official JetBrains site:<\/p>\n

\"teamcity-site-deploy-2-azure\"<\/a><\/p>\n

The offer lets you run a JetBrains TeamCity<\/a> server and a local agent on an Azure Linux VM in Azure.<\/p>\n

Today we\u2019ll go over a TeamCity instance setup on Azure, which will save you time and effort of configuration tasks.<\/p>\n

Prerequisites<\/h2>\n

You\u2019ll need an Azure subscription and about 10 minutes to set up TeamCity.
\nNote: Make sure you have a contributor and user access administrator roles<\/a> on Azure.<\/p>\n

Installation<\/h2>\n

Most of the TeamCity installation is automated, all you need to do is perform a few steps:<\/p>\n

    \n
  1. Log in to the Azure portal.<\/li>\n
  2. In your browser, open the TeamCity offer<\/a> in the Azure Marketplace.<\/li>\n
  3. Select GET IT NOW<\/li>\n
  4. Review the pricing and terms information, select Continue<\/b>.<\/li>\n
  5. Select Create<\/b> at the bottom of the page to configure a TeamCity installation.<\/li>\n
  6. Configure settings:\n
      \n
    1. In the Basics <\/b>tab, create a new resource group, in our case teamcity_demo:<\/li>\n
    2. Configure Virtual machine settings: provide the username and authentication type. The recommended approach is to use SSH key for that. Password authentication is not recommended due to the known issue with CoreOS metadata<\/a> service which breaks the startup of the default build agent. The Domain name label, DNS Prefix for the TeamCity server, will be auto-filled for you. If editing it, make sure it is globally unique.
      \nAt this step, you also need to configure and save the subnet settings. Click OK to save the Virtual Machine settings.<\/li>\n
    3. On the Additional Settings<\/b> tab, select the TeamCity installation size and provide a password for the MySQL database of your TeamCity instance.<\/li>\n
    4. Review the summary on the next screen. If required, download the template and parameters on your local machine for future use. Go on creating the TeamCity instance by clicking Ok.<\/b><\/li>\n<\/ol>\n<\/li>\n
    5. Review the privacy policy and if you agree, proceed by using Create<\/b>. The deployment in progress message appears and you can click on it or the notification icon at the top to review the progress. The Operation Details link can be useful if an error occurs.<\/li>\n
    6. Click Refresh. Upon a successful installation you\u2019ll see the TeamCity URL name in the deployment Outputs <\/b>tab:
      \n      \"teamcity-outputs-DNS\"<\/a><\/li>\n<\/ol>\n

      That\u2019s it! Now you can use the URL to access your TeamCity instance: you\u2019ll need to accept the license agreement and set up the administrator account credentials.<\/p>\n

      You are ready to use your TeamCity installation, which includes the server and one local agent. See the TeamCity Quick start guide to configure and run your first build<\/a>.<\/p>\n

      You might also want to expand your installation and make it more flexible by performing a couple of additional steps.<\/p>\n

      Adding Azure agents<\/h3>\n

      Your TeamCity setup includes a TeamCity server and a local agent. You can add more agents to your installation using the cloud profile:<\/p>\n

      In the TeamCity Web UI, go to the Project Settings |<\/b> Cloud Profiles<\/b> and select Azure to create a cloud profile to start TeamCity agents:\"teamcity-profile\"<\/a><\/p>\n

      Configure a VM image:<\/p>\n

      Select teamcity-demo resource group, set container (preview) as the image type, and specify the jetbrains\/teamcity-agent docker image. Configure the remaining settings and save them.<\/p>\n

      Note that specifying the storage account will persist container volumes in Azure, preventing the agent upgrade on each start.<\/p>\n

      \"teamcity-profile-image\"<\/a><\/p>\n

      After you finish the setup, it\u2019ll take the agent about 10 min to connect to the TeamCity server: this time is required to start a VM from the created image, then the machine needs to download all the required plugins, etc.<\/p>\n

      The connected agent will be visible on the agent page:<\/p>\n

      \"teamcity_agents2\"<\/a><\/p>\n

      Configuring artifact storage<\/h3>\n

      By default, TeamCity uses built-in storage for artifacts<\/a>. To switch to Azure cloud storage, perform the following:<\/p>\n

        \n
      1. In the TeamCity Web UI, go to the Project Settings | Artifacts Storage<\/b> tab. The built-in TeamCity artifacts storage is displayed by default and marked as active.<\/li>\n
      2. Click Add new storage<\/b>. Select Azure as the storage type. Optionally, provide a name for your storage.<\/li>\n
      3. Supply your storage credentials:\n
          \n
        1. in the Azure portal, go to Storage accounts -> Access keys and copy the storage account name<\/li>\n
        2. paste it to the account name in the TeamCity.<\/li>\n
        3. Perform the same for the key – any of the two keys available on the portal will work.<\/li>\n<\/ol>\n<\/li>\n
        4. Save your settings.<\/li>\n
        5. The configured Azure storage will appear on the Artifacts storage page. Make it active using the corresponding link.
          \n          \"teamcity-artifact-storage-active\"<\/a><\/li>\n<\/ol>\n

          Now TeamCity will store build artifacts externally.<\/p>\n

          Happy building!<\/em><\/p>\n","protected":false},"author":236,"featured_media":0,"comment_status":"open","ping_status":"open","template":"","categories":[11,89,12],"tags":[91],"cross-post-tag":[],"acf":[],"_links":{"self":[{"href":"https:\/\/blog.jetbrains.com\/fr\/wp-json\/wp\/v2\/teamcity\/12715"}],"collection":[{"href":"https:\/\/blog.jetbrains.com\/fr\/wp-json\/wp\/v2\/teamcity"}],"about":[{"href":"https:\/\/blog.jetbrains.com\/fr\/wp-json\/wp\/v2\/types\/teamcity"}],"author":[{"embeddable":true,"href":"https:\/\/blog.jetbrains.com\/fr\/wp-json\/wp\/v2\/users\/236"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.jetbrains.com\/fr\/wp-json\/wp\/v2\/comments?post=12715"}],"version-history":[{"count":0,"href":"https:\/\/blog.jetbrains.com\/fr\/wp-json\/wp\/v2\/teamcity\/12715\/revisions"}],"wp:attachment":[{"href":"https:\/\/blog.jetbrains.com\/fr\/wp-json\/wp\/v2\/media?parent=12715"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.jetbrains.com\/fr\/wp-json\/wp\/v2\/categories?post=12715"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.jetbrains.com\/fr\/wp-json\/wp\/v2\/tags?post=12715"},{"taxonomy":"cross-post-tag","embeddable":true,"href":"https:\/\/blog.jetbrains.com\/fr\/wp-json\/wp\/v2\/cross-post-tag?post=12715"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}