<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!--
- Licensed Materials - Property of IBM* and/or HCL**
- UrbanCode Deploy
- UrbanCode Build
- UrbanCode Release
- AnthillPro
- (c) Copyright IBM Corporation 2011, 2017. All Rights Reserved.
- (c) Copyright HCL Technologies Ltd. 2018. All Rights Reserved.
-
- U.S. Government Users Restricted Rights - Use, duplication or disclosure restricted by
- GSA ADP Schedule Contract with IBM Corp.
-
- * Trademark of International Business Machines
- ** Trademark of HCL Technologies Limited
--><pluginInfo>
  <!--

  **author name IS required**

  The Author Section is used to give credit to the author of the plugin.
  Name is the only required element/attribute, but feel free to also include your email,
  website  or bio to allow users of your plugin to praise your work, ask questions
  or share their use case to help grow your plugin's functionality.
  -->

  <author name="UrbanCode">
    <organization>UrbanCode</organization>
    <email>info@urbancode.com</email>
    <website>http://urbancode.com</website>
    <bio/>
  </author>

  <!--

  **intergration type IS Required**

  The integration type section identifies where the plugin fits into the process
  excepted types are SCM, Build, Artifact, Automation, Deploy

  For example:

  The plugin pulls Artifacts from an artifact repository during deployment
  the Type would be "Artifact"
  or
  The plugin deploys to a middleware server
  the Type would be "Deploy"
  -->

  <integration type="Automation"/>


  <!--
  **source is NOT required**

  The source section identifies the location of the plugin source code
  For example
  https://github.com/...
  -->
  <!--
  <source url=""/>
  -->
  <!--
  **license type is NOT required**

  If your plugin uses any licensed software please acknowledge it by
  listing the license type below
  -->
  <!--
  <licenses>
    <license type=""/>
  </licenses>
  -->
  <!--
  **tool-description IS required**

  The tool-description section is used to summarize the software
  the plugin was created to integrate with.

  For example:
  Apache Ant is a software tool to automate software processes during the build or
  deployment of an application. Ant uses an propitiatory XML file to define build
  and/or deployment steps(referred to as targets by ant) . The Ant executable is
  called to execute the targets in the build.xml.
  -->

  <tool-description>uDeploy is Urbancode's application release automation tool. For more information, see http://www.urbancode.com/html/products/deploy</tool-description>

  <!--
  **related-info is NOT required**

  The releated-info section is used to define links which may be useful to users of the plugin
  but don't fall into the release-notes or tool-description section.

  For example: releated-info can be links to pdf documentation, help videos related to plugin setup or the product's
  website.

  excepted values for type include: PDF, WEBSITE, VIDEO
  -->
  <!--
  <related-info>
    <link title="" type="" description="" url =""/>
  </related-info>
  -->
  <!--
  **meta-html in NOT required**

  The meta-html section is used define the meta description and the meta keywords of the plugin page.The meta
  description tag allows you to influence the description of your page in the web crawlers that support the
  tag The meta keywords tag allows   you to provide additional text for crawler-based search engines to index
  along with your body copy.

  If multiple keywords are used they must be comma(,) delimited
  -->

  <meta-html>
    <meta content="" name="description"/>
    <meta content="" name="keywords"/>
  </meta-html>

  <!-- Do not change the release-version, the build process injects it. -->
  <release-version>82.1026765</release-version>

  <release-notes>
    <!--
      **release-note IS required**

      The plugin-version name must match the plugin version found in the plugin.xml file

      The release-note should document the changes, improvements, or bug fixes introduced
      with the new plugin version

      The release-note may contain text or reference a file in the plugin zip package

      For example your release note could be:
      Support for was added for version 10.0 for software X
      or
      releaseNotes/release1.html (where release1.html contains html formatted version information)
      -->

    <release-note plugin-version="4">
This is the initial release of this plugin.
    </release-note>
    <release-note plugin-version="5">
Added a step to get properties for a component/environment mapping.
    </release-note>
    <release-note plugin-version="7">
Added Check If Environment Exists, Verify Inventory Status, and Add User/Group To Role
    </release-note>
    <release-note plugin-version="8">
Added status check to Verify Inventory Status
    </release-note>
    <release-note plugin-version="9">
Added a Delete Environment step to delete environments. This step will only work with versions 4.8.1 and higher.
    </release-note>
    <release-note plugin-version="11">
Improved steps to create environments so more information can be provided upfront in a single step.
    </release-note>
    <release-note plugin-version="61">
Updated to new security model.
    </release-note>
    <release-note plugin-version="62">
Added Add Base Resource step.
    </release-note>
    <release-note plugin-version="63">
Added Get Latest Version By Environment and Component step.
    </release-note>
    <release-note plugin-version="64">
Removed Inactivate Environment step. Environments on 6.0 cannot be inactivated.
    </release-note>
    <release-note plugin-version="65">
Removed Create Component Mapping step. Component Mappings are not present in Deploy 6.x.
    </release-note>
    <release-note plugin-version="66">
Added fields for the Create Environment step so it can provision environments using blueprints
    </release-note>
    <release-note plugin-version="67">
Added a step to get basic information about an environment.
    </release-note>
    <release-note plugin-version="68">
Added field to specify environment profile when creating an environment.
    </release-note>
    <release-note plugin-version="69">
Added field to specify node properties for cloud environments when creating an environment.
    </release-note>
    <release-note plugin-version="70">
Fixed APAR PI58277 - Verify Inventory Status step not working on version 6.1.1.3 of UrbanCode Deploy.
    </release-note>
    <release-note plugin-version="71">
Fixed APAR PI45948 - Set environment property step may fail if run simultaneously.
    </release-note>
    <release-note plugin-version="72">
Fixes APAR PI57417. Plug-in now checks the agent settings for acceptance of self signed certificates.
    </release-note>
    <release-note plugin-version="73">
Support property file encryption.
    </release-note>
    <release-note plugin-version="74">
RFE 83705 - Added Create Environment from Template step.
    </release-note>
    <release-note plugin-version="75">
RFE 100937 Added 'Create Multiple Environments' step to create multiple environments using json.
RFE 100937 Altered 'Add Environment to Team' step to allow for multiple environments.
    </release-note>
    <release-note plugin-version="76">
Fixed typo in 'Create Multiple Environments' description
    </release-note>
    <release-note plugin-version="77">
Update for API changes in server.
    </release-note>
    <release-note plugin-version="78">
Plugin name changed.
    </release-note>
    <release-note plugin-version="79">
RFE 121148 Removed 'isSecure' property from 'Set Component Environment Property' to support property definition type.
    </release-note>
    <release-note plugin-version="80">
Fixed APAR PI97913 - Create Environment can accept more than 20 properties
    </release-note>
    <release-note plugin-version="81">
Add "Secure Value" field to "Create Environment Property" step.
    </release-note>
    <release-note plugin-version="82">
        Fixing CVE:CVE-2019-4233
    </release-note>

  </release-notes>
</pluginInfo>
