<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Deepthi Bhat on Medium]]></title>
        <description><![CDATA[Stories by Deepthi Bhat on Medium]]></description>
        <link>https://medium.com/@deepthikbhat95?source=rss-114e132ff37------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*EiVUCkq2tK_tn2E7</url>
            <title>Stories by Deepthi Bhat on Medium</title>
            <link>https://medium.com/@deepthikbhat95?source=rss-114e132ff37------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 03:23:18 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@deepthikbhat95/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[CI/CD using Visual Studio Team Services [VSTS]-Octopus Deploy for a .NET web application — Part 1]]></title>
            <link>https://medium.com/@deepthikbhat95/ci-cd-using-visual-studio-team-services-vsts-octopus-deploy-for-a-net-web-application-part-1-7b9479db3eaa?source=rss-114e132ff37------2</link>
            <guid isPermaLink="false">https://medium.com/p/7b9479db3eaa</guid>
            <category><![CDATA[deployment-pipelines]]></category>
            <category><![CDATA[octopus-deploy]]></category>
            <category><![CDATA[azure]]></category>
            <category><![CDATA[vsts]]></category>
            <dc:creator><![CDATA[Deepthi Bhat]]></dc:creator>
            <pubDate>Tue, 31 Jul 2018 09:51:25 GMT</pubDate>
            <atom:updated>2018-07-31T09:52:22.990Z</atom:updated>
            <content:encoded><![CDATA[<p>Are you a Developer or a DevOps Engineer?</p><p>Does the name Jenkins ring not just a bell but a gong in your head? Do regular discussions revolve around how long your build jobs on Jenkins take and how you never seem to get priority on that elusive Jenkins agent.</p><p>Well we have been there and are happy to say that while we may not have discovered the El Dorado for all these problems. We do have something that might get you to sit back and take a sigh of relief.</p><p>Enter Microsoft VSTS, which will no longer ask you to download MSIs or EXEs but instead, will politely ask for an instance name and provision one for you on the cloud. Even the agent will be provided to you on the fly, hosted through Azure. Now ain’t that much better than the usual round of the mill — Continuous Integration [CI] tasks we all are so familiar with.</p><p>Now that we have blown your mind off with VSTS, we would also like to make a humble mention of Octopus Deploy. These guys are inconspicuously making a lot of waves in the Continuous Deployment [CD] world.</p><p>They provide a lot of extensions that will plugin to any target technology stack. They have an in-house file management system for artifacts, environment and config management. All the makings of a great CD tool. And the icing on the cake is their Rest API support which is pro automation.</p><p>One could argue that the same features are provided in VSTS too. But, where Octopus Deploy scores is the ease with which you can find out which version of the product is deployed to which environment. Octopus Deploy has a dedicated support team, always ready to answer any queries. And last but not the least, they have a stellar documentation with well explained processes and diagrams as opposed the scattered documentation for VSTS.</p><p>So, when you have a great CI and CD tool, it is only fair that we demonstrate how well they work together. Here’s our two cents on how to setup a CI-CD pipeline with VSTS and Octopus Deploy for a DOTNET project.</p><h3>Prerequisites</h3><p>· VSTS account. If you don’t have one, you can create from <a href="https://www.visualstudio.com/">here</a></p><p>· Octopus deploy server. If you don’t have one, you can download and set up following the instructions from <a href="https://octopus.com/">here</a></p><p>· In the <em>Octopus Deploy Server</em> dashboard, go to the<strong> User Profile</strong> and select <strong>API keys</strong>. Select <em>New API key</em>. Record the purpose of this key in <em>Purpose</em> and click on <strong>Generate New</strong>. Copy and save the generated API key to use the same for integrating Octopus Deploy with VSTS.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/702/1*jsF8wZRaef7CdtTc1B7i4A.png" /></figure><p>· In VSTS, click on <strong>Settings</strong> and go to <strong>Services.</strong> Select <strong>New Service Endpoint </strong>and choose <strong>Octopus Deploy</strong> in the drop down. Add a connection name of your choosing and paste the <em>Octopus deploy server URL</em> and <em>API key</em> generated in the Octopus server.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/705/1*JSDbErh-UPh5eiBXFQ5Isg.png" /></figure><p>· Azure subscription to create Azure Web App.</p><p>· In Azure portal, click on <strong>App Services </strong>and<strong> </strong>select <strong><em>Microsoft Web App. </em></strong>Provide a <em>name for the web application</em>, <em>create or use an existing resource group</em> and click on create.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/572/1*CvnkKn2BlY-dqH-qZmEopw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/262/1*qOsnIIERd1PwEsObMuopMw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/691/1*JDuZRVxVWFxQp4Qzbyuf5Q.png" /></figure><p>· Sample code <a href="https://github.com/Microsoft/myhealthclinic2017">link</a></p><p>· Install <em>VSTS add-on</em> <strong>Octopus Deploy Integration</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/583/1*7BuXkSEfAUKSMTfKDIa_hA.png" /></figure><h3>Octopus Deploy</h3><p>To get a better picture about Octopus Deploy, we’ll to a little in depth about how the octopus deploy workflow is designed and how the resources are linked. The deployment process is used for deploying the software by adding steps and variables to a project.</p><p><strong>Projects </strong>contain the deployment steps and configuration variables that define how the software is deployed.</p><p><strong>Lifecycles</strong> control how the software is promoted through your environments and which projects are associated with which environments. A lifecycle may have different <strong>Phases </strong>and each Phase may be associated with a different <strong>environment. </strong>It is possible to<strong> </strong>add one or multiple environments or leave the default Any Environments option selected. If <strong>Any Environments</strong> is chosen, this phase of the Lifecycle will deploy to all the environments that haven’t been explicitly added to the Lifecycle in previous phases. Any future environments defined will also be deployed to as part of this phase of the Lifecycle. The Default Lifecycle looks like this -</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/240/1*rVMd0V13njnc3CRVFCvI_w.png" /></figure><p>Using Octopus Deploy you can deploy software to Windows servers, Linux servers, Microsoft Azure, AWS, an offline package drop, or cloud regions. These machines and services are your <strong>deployment targets</strong>. Octopus organizes the deployment targets into groups called <a href="https://octopus.com/docs/infrastructure/environments"><strong>environments</strong></a>. Typical environments are <strong>Development, Test</strong>, and <strong>Production</strong>.</p><p>After you have defined your lifecycles, they become available to your projects. Projects can be deployed to any environment in their lifecycle.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/590/1*xyzIaEsYp6RTaQLumQhrjw.png" /></figure><p>Variables make it easier to define application settings for your deployment processes without the need to hardcode them. For instance, you might use different connection strings for apps deployed to Test and Production. Variables let you define these settings and then refer to them by the variable name throughout the deployment process, meaning you don’t have to manually change them between deployments. Variables are essentially name/value pairs with optional scope rules applied. You can edit the variables using the <strong>Variables </strong>tab within a project.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/645/1*zaOa_qFbWj0FM8bHPrT1Ng.png" /></figure><h3>Connecting Azure to Octopus Deploy</h3><p>1. Log in to your Azure Account through the <a href="https://portal.azure.com/">Azure portal</a>.</p><p>2. Select <strong>Azure Active Directory</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/223/1*8tdkD1aVKu7cP81-krNukQ.png" /></figure><p>3. Select <strong>App registrations</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/222/1*_fEttffpGbwgQBcwrfImfQ.png" /></figure><p>4. Select <strong>New application registration</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/404/1*2BjslihQ1OSAcgyiZO_v0g.png" /></figure><p>5. Provide a name and URL for the application. Select <strong>Web app / API</strong> for the type of application you want to create. After setting the values for Octopus Deploy, select <strong>Create</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/297/1*BplolWpVobuWsO3beOJVSw.png" /></figure><p>You have created your application.</p><h3>Integrating Azure Account in Octopus Deploy</h3><p>Navigate to Infrastructure ➜ Accounts and click <em>Add Account</em> in the <em>Azure Subscriptions</em> section.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/1*FzZU4XyZ2qhoNuk2M29eSQ.png" /></figure><p>Octopus Deploy authenticates with Azure in one of two methods: using a <em>Management Certificate</em> or a <em>Service Principal</em>. Select <em>Use a Service Principal</em>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/564/1*RPh6NrIrwLwa70Q99olvZg.png" /></figure><h3>Details you need from Azure</h3><p><strong>Subscription ID</strong>: The ID of the Azure Subscription this account will interact with. In the Azure Portal, this can be found in the properties of the subscription.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/619/1*lzaDrnpfZM-HFHl-zI9plQ.png" /></figure><p><strong>AD Client\Application ID</strong>: This is the ID of the application in Azure Active Directory. In the new Azure Portal, it can be found under the <em>App registrations</em> blade in the <em>Azure Active Directory</em>. In the old Azure Portal, it may be listed as ‘Client ID’.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/207/1*iLbxlru2vwWLI_k1xRNqYg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/222/1*_fEttffpGbwgQBcwrfImfQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/1*oBYfItDOGXNesLIyChW7ag.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/1*N0YHilEin56NpMy722tPfw.png" /></figure><p><strong>AD Tenant ID</strong>: The ID of the Active Directory tenant. You can find this in the <em>Properties</em> blade of the <em>Azure Active Directory</em>, listed as ‘Directory ID’.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/171/1*lTftAOCtCUut3_N6dlu10g.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/1*N-sFGLA4I0wcmG65dif_ZA.png" /></figure><p><strong>AD Password\Key</strong>: The password for the Azure Active Directory application: this is known as ‘Password’ in the API or ‘Key’ in the Azure Portal. New keys can be generated in the portal under the <em>Keys</em> blade of the Azure Active Directory application.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/261/1*JDPsYTiqMvNMkV-jjOGvZg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/296/1*ixBN4WP_9DKY1t9At8DeMg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/1*Bo_9O_0BrHA5hkI9nmuNug.png" /></figure><p>Use the <em>Save and test</em> button to confirm the account can interact with Azure.</p><p>Now that we have all the pieces of the puzzle lined up, let’s head over to <a href="https://medium.com/@deepthikbhat95/ci-cd-using-visual-studio-team-services-vsts-octopus-deploy-for-a-net-web-application-part-2-52bb033d62a4">Part 2</a> which will talk about how to set up the build in VSTS and the deployment in Octopus Deploy.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7b9479db3eaa" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[CI/CD using Visual Studio Team Services [VSTS]-Octopus Deploy for a .NET web application — Part 2]]></title>
            <link>https://medium.com/@deepthikbhat95/ci-cd-using-visual-studio-team-services-vsts-octopus-deploy-for-a-net-web-application-part-2-52bb033d62a4?source=rss-114e132ff37------2</link>
            <guid isPermaLink="false">https://medium.com/p/52bb033d62a4</guid>
            <category><![CDATA[vsts]]></category>
            <category><![CDATA[azure]]></category>
            <category><![CDATA[continuous-integration]]></category>
            <category><![CDATA[octopus-deploy]]></category>
            <dc:creator><![CDATA[Deepthi Bhat]]></dc:creator>
            <pubDate>Tue, 31 Jul 2018 09:51:06 GMT</pubDate>
            <atom:updated>2018-07-31T09:52:00.238Z</atom:updated>
            <content:encoded><![CDATA[<p>In retrospect, <a href="https://medium.com/@deepthikbhat95/ci-cd-using-visual-studio-team-services-vsts-octopus-deploy-for-a-net-web-application-part-1-7b9479db3eaa">Part 1</a> outlined a brief overview of why we chose VSTS and Octopus Deploy for our CI-CD pipeline. We also described what prerequisites we need for the latter. Now, we get into the details of the actual pipeline.</p><p>From your VSTS account overview page, select <strong>New Project</strong>, provide a name for your new Team project, select its initial source control type, and select a process to create a team project. On moving to the next page, select <strong>build code from an external repository</strong> and <strong>Setup Build.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/690/1*XryREFiiM-nnyikU2snD7Q.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/614/1*grg0Dw-SDSGY7ru30sFWVQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/1*mfNRHsRnGFH4o8jpXVTPKA.png" /></figure><p>You can fetch your code from various sources including <strong><em>VSTS, SVN, or any other Git repository</em></strong> but in this example,<strong><em> </em></strong>select <strong>GitHub</strong> as the source and <strong>authorize the GitHub connection using OAuth.</strong> Once the authorization is successful, select the repository and default branch for builds.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/1*9A4YQLUDcT-fVkkYyVi4Kg.png" /></figure><p>You can start by selecting a template that will add a set of tasks and apply typical settings for the kind of application that you are building for or start with an empty template and build from scratch. In this case, apply <strong>ASP.NET Core template</strong> to set up the build.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/669/1*rK_WTud8r9-gW-OKdl8ltw.png" /></figure><p>The build steps are explained in the following screenshots below.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/576/1*qFjluAkkv5DEygLjoXUnxA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*F5G7hD52k0tgWKk3lC6LHA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/584/1*7UunuZ_ClyroO3OWBAKAJQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/587/1*9l8ADkjRKtqvadBeMyC3Tg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/725/1*AP77keebMWGheQyJTH_Xjg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/650/1*5gguT8QDVfiFXYhZJIkweQ.png" /></figure><p>In the <strong>Push Package(s) to Octopus</strong> task of the build definition, select the Octopus deploy server connection you have added in the service endpoint. Add the package file path to push to Octopus. This is as follows in this example- <strong>D:\a\1\a\MyHealth.Web.3.5.$(build.buildnumber).zip</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/642/1*6dLkmPTs2GYTDRv5b0Sltw.png" /></figure><p>Enable GitHub commit build triggers by selecting the option <strong>Enable continuous integration </strong>and choose the branch which must trigger the builds. Save the build definition.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/614/1*K0rD3gZQxWe_vQ0OhUSlTg.png" /></figure><p>Now, your project is ready for build. Click on <strong>Queue</strong> and the build starts.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/784/1*7WkYBk1ppcA5bFnC1lyUwA.png" /></figure><p>Click on releases and select <strong>New Definition</strong>. On selecting New Definition, a list of templates is made available. Select <strong>Empty process</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/602/1*qDgaWCXANGPLiKTlEltomw.png" /></figure><p>Click on <strong>Add artifact</strong> and it will provide you with the several options for source type. In this example, select <strong>Build</strong> and select the <em>Project</em> and <em>Source</em> for artifact.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/669/1*wF6IWntVAWRaWr7qxqi0MQ.png" /></figure><p>Click on <em>Environment 1</em> and rename it to <strong>DEV</strong>. Click on the <strong>Agent Phase</strong> to add tasks. Add <strong>Create Octopus Release</strong> task and select the <em>Octopus Deploy Server</em> and <em>Project</em> from the drop down available.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/636/1*gjL37S06mBUaZbOGUUA2Og.png" /></figure><p>Add another task to <strong>Deploy Octopus Release</strong>. Select the <em>Octopus Deploy Server</em>, the <em>Project</em> and <em>the environment to which to deploy from</em> the drop down available. Save the release.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/570/1*tsX93HLWHVvRUo6jpcvLbA.png" /></figure><p>Click on <strong>Pipeline</strong> and select <strong>Add Environment</strong>. Rename the environment to <strong>QA</strong> and add <strong>Promote Octopus Release</strong> task. Specify the <em>Octopus Deploy server, Project name, the environment from which to Promote</em> and <em>the environment to which to Promote</em>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/667/1*lMx_dy9W4VQnoW4ilN6diA.png" /></figure><p>Once again, click on <strong>Pipeline</strong> and select the <em>approver gateway</em>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/663/1*nPGx_0yPVPXgfOdlRJCaKA.png" /></figure><p>Enable <strong>Pre-deployment approval</strong> for QA environment and select users for approval.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/619/1*AAJ7OWnm18BsasM2r3CjDg.png" /></figure><p>Click on <strong>Create Release</strong> and <em>DEV deployment</em> begins. On successful deployment of DEV environment in VSTS it <em>triggers the DEV deployment</em> in <em>Octopus Deploy </em>by creating and deploying the release in Octopus Deploy. This is followed by <em>QA environment deployment</em> on <strong>manual approval</strong> by the user in VSTS. This can be observed in the following screenshots.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/592/1*yUcMGrDxoVDcupCIKuUaHg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/517/1*P294Sa9ZB4oHRb9LnKJSlQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/588/1*cjhUgBkYHgoCCDxz0wlRog.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/638/1*7flgI_jJp1qqFW8nLZYJtg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/590/1*_4wa_PPC5cd8P4Co1Zgf-Q.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/544/1*5Wr6ZXUfP-B2odlO8cqkHg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/537/1*AsM9r_t6iisrrbHUwX8zpQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/577/1*JX90mh1nC1-0CTuiUkRvBQ.png" /></figure><h3>On a parting note</h3><p>We hope to have piqued your interest in using VSTS and Octopus Deploy for your CI-CD needs. As always, there is a question — “What next?”. To answer that, we can set up the whole pipeline using Rest APIs and a scripting language of our choice. Should you be interested in doing that, please look forward for more articles from us.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=52bb033d62a4" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>