xpresso plugin release v20.8

Author: ke-liu

README.md

@@ -25,3 +25,5 @@ https://github.com/CiscoTestAutomation/jenkins_project_plugin/blob/master/README
 * [2018](changelog/2018/CHANGELOG.md)
 
 * [2019](changelog/2019/CHANGELOG.md)
+
+* [2020](changelog/2020/CHANGELOG.md)

changelog/2020/AUG.md

@@ -0,0 +1,5 @@
+| Date          | Version       |
+| ------------- |:-------------:|
+| Aug 25        | 20.8          |
+
+* Support Xpresso job/profile 'description' and other meta data in Json format to request.

changelog/2020/CHANGELOG.md

@@ -0,0 +1,3 @@
+# 2020
+
+* [August](AUG.md)

downloads/v20.8/.DS_Store

@@ -60,11 +60,13 @@ Provide the information about the Xpresso job to be executed.
 * "Job name" and "profile" are mandatory when no "Bundle profile" has been specified. If "Bundle profile" is provided, do not specify the following fields: "Job name", "Profile", "Testbeds", "Topology".
 * The "Testbeds" and "Topology" are optional, if not been provided the default values configured in Xpresso will be used. "Testbeds" and "Topology" are mutually exclusive, only one can be provided.
 * "Send topology email" is optional. To send topology email, "Topology" field has to be specified.
+* The "Tags" is optional. It allows user to specify a list of tags associated with the Xpresso job.
+* The "Description" is optional. It allows user to specify Xpresso job/profile description, with max length 256 characters.
 * The "Max Request Lifetime" is the maximum duration for the Request to get Completed until it is stopped.  
 * Select the "Block until completed" to block running the next build step until the current build step is completed. The status of the current build step is checked periodically (every 2 minutes). The Xpresso job status URL will be provided on the console.
 * "Environment variables", "Job arguments", and "Harness arguments" are hidden under "Xpresso arguments (variables)" button. These are optional info, and they took Json format. A basic form validation will be performed against Json format while user configure these values. They will also accept the variable substitutions. User can define native Jenkins 'multi-line string' parameters and use them in these fields. No Json validation will be performed when use variables for these fields.
 * "Clean" is optional. If checked, plugin uses default clean instruction to clean the selected testbed(s) before running. Only testbeds with a configured clean instruction will be cleaned. "Clean info" is also optional. It accept Json format input or variable substitution. once be specified, it overwrites the default clean instruction registered on Xpresso.
-* "Meta text", and "Meta files" are hidden under "Meta data" button. These are optional fields. "Meta text" allows user add any text based content in the request. "Meta files" takes a list of file paths (separated with space). The contents of the files will be added into the request when submitting the build to the xpresso. User should expect to see these meta info attached on the email report by the end of the execution.
+* "Meta text", "Meta files" and "Other meta info" are hidden under "Meta data" button. These are optional fields. "Meta text" allows user add any text based content in the request. "Meta files" takes a list of file paths (separated with space). The contents of the files will be added into the request when submitting the build to the xpresso. User should expect to see these meta info attached on the email report by the end of the execution."Other Meta info" allows user add any Json content in the request.
 * "Xpresso instance URL", and "Xpresso token" are hidden under "Advanced..." button. These are optional fields. If configured, plugin ignores the pre-registered Xpresso settings ('Registered Xpresso URL' and 'Registered user ID') and use these project level authentication to communicate with the Xpresso.
 
 ![](assets/images/buildconfig3.png)