<?xml version="1.0" encoding="UTF-8"?><rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>deployingsoftware —   christova  </title>
    <link>https://christova.writeas.com/tag:deployingsoftware</link>
    <description>&lt;b&gt;&lt;h3&gt;Tech Articles&lt;/h3&gt;&lt;/b&gt;&lt;br/&gt;&lt;b&gt;Collated from various sources. Full copyright remains with original authors.&lt;/b&gt;</description>
    <pubDate>Mon, 16 Nov 2026 16:52:49 +0000</pubDate>
    <item>
      <title>How Companies Ship Code</title>
      <link>https://christova.writeas.com/how-companies-ship-code?pk_campaign=rss-feed</link>
      <description>Step 1: The process starts with a product owner creating user stories based on requirements. Step 2: The dev team picks up the user stori...</description>
      <content:encoded><![CDATA[<p><img src="https://i.snap.as/tsR3Ww9R.jpg" alt=""/></p>

<p><strong>Step 1</strong>: The process starts with a product owner creating user stories based on requirements.</p>

<p><strong>Step 2</strong>: The dev team picks up the user stories from the backlog and puts them into a sprint for a two-week dev cycle.</p>

<p><strong>Step 3</strong>: The developers commit source code into the code repository Git.</p>

<p><strong>Step 4</strong>: A build is triggered in Jenkins. The source code must pass unit tests, code coverage threshold, and gates in SonarQube.</p>

<p><strong>Step 5</strong>: Once the build is successful, the build is stored in artifactory. Then the build is deployed into the dev environment.</p>

<p><strong>Step 6</strong>: There might be multiple dev teams working on different features. The features need to be tested independently, so they are deployed to QA1 and QA2.</p>

<p><strong>Step 7</strong>: The QA team picks up the new QA environments and performs QA testing, regression testing, and performance testing.</p>

<p><strong>Steps 8</strong>: Once the QA builds pass the QA team’s verification, they are deployed to the UAT environment.</p>

<p><strong>Step 9</strong>: If the UAT testing is successful, the builds become release candidates and will be deployed to the production environment on schedule.</p>

<p><strong>Step 10</strong>: SRE (Site Reliability Engineering) team is responsible for prod monitoring.</p>

<p><a href="https://christova.writeas.com/tag:environments" class="hashtag" rel="nofollow ugc"><span>#</span><span class="p-category">environments</span></a> <a href="https://christova.writeas.com/tag:code" class="hashtag" rel="nofollow ugc"><span>#</span><span class="p-category">code</span></a> <a href="https://christova.writeas.com/tag:production" class="hashtag" rel="nofollow ugc"><span>#</span><span class="p-category">production</span></a> <a href="https://christova.writeas.com/tag:DeployingSoftware" class="hashtag" rel="nofollow ugc"><span>#</span><span class="p-category">DeployingSoftware</span></a></p>
]]></content:encoded>
      <guid>https://christova.writeas.com/how-companies-ship-code</guid>
      <pubDate>Tue, 12 Nov 2024 10:57:15 +0000</pubDate>
    </item>
  </channel>
</rss>