<?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 Re: How do we export a Release(example from dev environment)  with CLI and import to different environment (test) of BP in Product Forum</title>
    <link>https://community.blueprism.com/t5/Product-Forum/How-do-we-export-a-Release-example-from-dev-environment-with-CLI/m-p/99571#M47109</link>
    <description>&lt;P&gt;&lt;SPAN&gt;For a package that already exists, create a release and export it using:&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;EM&gt;AutomateC /exportpackage "HR Processes" /release "v1.4" /sso&lt;/EM&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;If the &lt;/SPAN&gt;/release &amp;lt;release_name&amp;gt;&lt;SPAN&gt; parameter is not specified, the name of the release will automatically be set to “&lt;STRONG&gt;&amp;lt;package_name&amp;gt; - Release #&lt;/STRONG&gt;”, where the release number is incremented automatically.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Note that the package itself, where various processes, objects, tiles etc. are grouped must be created through the GUI first.&amp;nbsp; The .bprelease file will be exported to the folder where the command was executed and requires write permission to that folder.&amp;nbsp; &lt;/SPAN&gt;&lt;/P&gt;</description>
    <pubDate>Fri, 28 May 2021 04:14:42 GMT</pubDate>
    <dc:creator>james.man</dc:creator>
    <dc:date>2021-05-28T04:14:42Z</dc:date>
    <item>
      <title>How do we export a Release(example from dev environment)  with CLI and import to different environment (test) of BP</title>
      <link>https://community.blueprism.com/t5/Product-Forum/How-do-we-export-a-Release-example-from-dev-environment-with-CLI/m-p/99570#M47108</link>
      <description>I'm able to import in the same environment tough with&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;.\automatec.exe /sso / Importrelease&amp;nbsp; &amp;lt;releasepath&amp;gt;</description>
      <pubDate>Thu, 27 May 2021 18:58:15 GMT</pubDate>
      <guid>https://community.blueprism.com/t5/Product-Forum/How-do-we-export-a-Release-example-from-dev-environment-with-CLI/m-p/99570#M47108</guid>
      <dc:creator>Vikas</dc:creator>
      <dc:date>2021-05-27T18:58:15Z</dc:date>
    </item>
    <item>
      <title>Re: How do we export a Release(example from dev environment)  with CLI and import to different environment (test) of BP</title>
      <link>https://community.blueprism.com/t5/Product-Forum/How-do-we-export-a-Release-example-from-dev-environment-with-CLI/m-p/99571#M47109</link>
      <description>&lt;P&gt;&lt;SPAN&gt;For a package that already exists, create a release and export it using:&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;EM&gt;AutomateC /exportpackage "HR Processes" /release "v1.4" /sso&lt;/EM&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;If the &lt;/SPAN&gt;/release &amp;lt;release_name&amp;gt;&lt;SPAN&gt; parameter is not specified, the name of the release will automatically be set to “&lt;STRONG&gt;&amp;lt;package_name&amp;gt; - Release #&lt;/STRONG&gt;”, where the release number is incremented automatically.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Note that the package itself, where various processes, objects, tiles etc. are grouped must be created through the GUI first.&amp;nbsp; The .bprelease file will be exported to the folder where the command was executed and requires write permission to that folder.&amp;nbsp; &lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 28 May 2021 04:14:42 GMT</pubDate>
      <guid>https://community.blueprism.com/t5/Product-Forum/How-do-we-export-a-Release-example-from-dev-environment-with-CLI/m-p/99571#M47109</guid>
      <dc:creator>james.man</dc:creator>
      <dc:date>2021-05-28T04:14:42Z</dc:date>
    </item>
  </channel>
</rss>

