<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic BP Auto Deployment Cookbook BP-GIT-Jenkins in Product Forum</title>
    <link>https://community.blueprism.com/t5/Product-Forum/BP-Auto-Deployment-Cookbook-BP-GIT-Jenkins/m-p/80940#M32579</link>
    <description>&lt;SPAN lang="EN-GB" style="margin: 0px; color: #000000; font-size: 12pt;"&gt;&lt;SPAN style="font-family: Calibri Light;" color="#000000" face="Calibri Light"&gt;In the past few years, I have been involved in several ROM Assessments for Customers.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN lang="EN-GB" style="margin: 0px; color: #000000; font-size: 12pt;"&gt;&lt;SPAN style="font-family: Calibri Light;" color="#000000" face="Calibri Light"&gt;In many cases, I have observed that most of the Release management activities are done manually either by the support team or with the developer's assistance. This kind of deployment leaves a loophole which is a red flag during audits with the possibility of unwanted problems later for large production changes like upgrades.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN lang="EN-GB" style="margin: 0px; color: #000000; font-size: 12pt;"&gt;&lt;SPAN style="font-family: Calibri Light;" color="#000000" face="Calibri Light"&gt;This got me thinking to my old SOA deployment days where we corrected this problem with Jenkins Auto deployment using GIT as the code repository. We also had a pipeline implemented for approvals to higher environments. Recalling that, I worked on a demo for a similar implementation for Blue Prism. &lt;BR /&gt;&lt;BR /&gt;Adding the guide with a few notes as an attachment to this post.&amp;nbsp;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN style="color: #000000; font-size: 12pt;"&gt;Hope it helps someone.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;------------------------------&lt;BR /&gt;Ashish Easow&lt;BR /&gt;Senior Consultant - Professional Services&lt;BR /&gt;Blueprism&lt;BR /&gt;&lt;BR /&gt;------------------------------&lt;BR /&gt;</description>
    <pubDate>Wed, 04 Mar 2020 05:00:00 GMT</pubDate>
    <dc:creator>ashish.easow</dc:creator>
    <dc:date>2020-03-04T05:00:00Z</dc:date>
    <item>
      <title>BP Auto Deployment Cookbook BP-GIT-Jenkins</title>
      <link>https://community.blueprism.com/t5/Product-Forum/BP-Auto-Deployment-Cookbook-BP-GIT-Jenkins/m-p/80940#M32579</link>
      <description>&lt;SPAN lang="EN-GB" style="margin: 0px; color: #000000; font-size: 12pt;"&gt;&lt;SPAN style="font-family: Calibri Light;" color="#000000" face="Calibri Light"&gt;In the past few years, I have been involved in several ROM Assessments for Customers.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN lang="EN-GB" style="margin: 0px; color: #000000; font-size: 12pt;"&gt;&lt;SPAN style="font-family: Calibri Light;" color="#000000" face="Calibri Light"&gt;In many cases, I have observed that most of the Release management activities are done manually either by the support team or with the developer's assistance. This kind of deployment leaves a loophole which is a red flag during audits with the possibility of unwanted problems later for large production changes like upgrades.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN lang="EN-GB" style="margin: 0px; color: #000000; font-size: 12pt;"&gt;&lt;SPAN style="font-family: Calibri Light;" color="#000000" face="Calibri Light"&gt;This got me thinking to my old SOA deployment days where we corrected this problem with Jenkins Auto deployment using GIT as the code repository. We also had a pipeline implemented for approvals to higher environments. Recalling that, I worked on a demo for a similar implementation for Blue Prism. &lt;BR /&gt;&lt;BR /&gt;Adding the guide with a few notes as an attachment to this post.&amp;nbsp;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN style="color: #000000; font-size: 12pt;"&gt;Hope it helps someone.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;------------------------------&lt;BR /&gt;Ashish Easow&lt;BR /&gt;Senior Consultant - Professional Services&lt;BR /&gt;Blueprism&lt;BR /&gt;&lt;BR /&gt;------------------------------&lt;BR /&gt;</description>
      <pubDate>Wed, 04 Mar 2020 05:00:00 GMT</pubDate>
      <guid>https://community.blueprism.com/t5/Product-Forum/BP-Auto-Deployment-Cookbook-BP-GIT-Jenkins/m-p/80940#M32579</guid>
      <dc:creator>ashish.easow</dc:creator>
      <dc:date>2020-03-04T05:00:00Z</dc:date>
    </item>
  </channel>
</rss>

