-
Notifications
You must be signed in to change notification settings - Fork 6
/
info.xml
92 lines (75 loc) · 4.69 KB
/
info.xml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!-- - Licensed Materials - Property of IBM Corp. - IBM UrbanCode Build -
IBM UrbanCode Deploy - IBM UrbanCode Releases - (c) Copyright IBM Corporation
2002, 2016. All Rights Reserved. - - U.S. Government Users Restricted Rights
- Use, duplication or disclosure restricted by - GSA ADP Schedule Contract
with IBM Corp. -->
<pluginInfo xmlns="http://www.urbancode.com/InfoXMLSchema_v1"
xmlns:server="http://www.urbancode.com/PluginServerXMLSchema_v1"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<!-- **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. Original author: <organization>IBM
ECM</organization> <email>yoavbe@il.ibm.com</email> -->
<author name="Bluemix">
<organization>IBM Bluemix</organization>
<email>gaas@us.ibm.com</email>
<website>http://bluemix.net</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="https://github.com/IBM-Bluemix/gp-ucd-plugin" />
<!-- **license type is NOT required** If your plugin uses any licensed software
please acknowledge it by listing the license type below -->
<licenses>
<license type="Apache-2.0" />
</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>The Bluemix Globalization Plugin allows users to use
Globalization Pipeline from IBM Bluemix.</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 -->
<!-- **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>
<release-version>1.02</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) To add a new release note add this with
a description in it of the changes: <release-note plugin-version="10">....</release-note>
Our automated release process will replace 'LATEST' with the released version.
If this already exists in the file, then the described changes have not been
released yet and you should just append to the existing 'LATEST' tag. -->
<release-note plugin-version="1.01">Release notes 1</release-note>
<release-note plugin-version="1.02">Documentation updates</release-note>
</release-notes>
</pluginInfo>