You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: guide/quick_start.md
+2-1Lines changed: 2 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -56,7 +56,7 @@ From the "Add build step" select __Execute Xpresso Job__. This can be repeated
56
56
### Step 3:
57
57
Provide the information about the Xpresso job to be executed.
58
58
59
-
* Complete the mandatory information such as: "Xpresso URL", "User ID", "Group name", and "Branch name".
59
+
* Complete the mandatory information such as: "Registered Xpresso URL", "Registered User ID", "Group name", and "Branch name".
60
60
* "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".
61
61
* 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.
62
62
* "Send topology email" is optional. To send topology email, "Topology" field has to be specified.
@@ -65,6 +65,7 @@ Provide the information about the Xpresso job to be executed.
65
65
* "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.
66
66
* "Clean info" is optional. It accept Json format input or variable substitution.
67
67
* "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.
68
+
* "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.
0 commit comments