Parameters - 6.7.0
|
Parameter |
Short |
Value |
Description |
---|---|---|---|---|
1 |
|
|
Content type to accept for renderRequest if different than type. |
|
2 |
a |
|
Requested operation to perform. Valid actions are listed at the end. |
|
3 |
|
|
Used in orderRepository to name the repository after which the repository will be positioned. Similarly for moveTask where it represent the name or id of the task. Similarly for moveStage where it represent the name of the stage. |
|
4 |
|
|
SQL to run after a successful action. Limited to specific actions at this time. |
|
5 |
|
|
Agent name. |
|
6 |
|
|
API version. Some requests produce different results based on the api version used. |
|
7 |
|
|
For some actions using the file parameter, append will append output to the existing file. |
|
8 |
|
|
Build artifact name. May be extended by a path name for locating files within an artifact representing a dirctory. |
|
9 |
|
|
Key used to identify a project, plan, or job to be assigned to a specific agent. This makes the agent dedicated to only perform builds for all assignments. Example: XXX, XXX-DEF, XXX-DEF-JOB1 |
|
10 |
|
|
Attribute to list. |
|
11 |
|
|
Indicate that a stage be run automatically. |
|
12 |
|
|
Before task name or id. |
|
13 |
|
|
Branch name. |
|
14 |
|
|
Build key. Normally used to refer to a specific build (3 or 4 part name). However, it was also an older terminology for a plan and some action continue to accept the older terminology. Example: XXX-DEF or XXX-DEF-1 |
|
15 |
|
|
Comma separated list of plan keys that represent child plan dependencies. |
|
16 |
|
|
Clean working directory after each job completes. Use on setJobOptions. |
|
17 |
|
|
For run actions, this option will automatically clear an existing file on the first append requested. |
|
18 |
|
|
Column selection and ordering when action generates CSV output. A comma separated list of column numbers (1-based) or column names (case insensitive). Only columns provided by the selected outputFormat are available for selection. Invalid columns will be ignored. |
|
19 |
|
|
Comment text. |
|
20 |
|
|
Common parameter string added to all run actions. |
|
21 |
|
|
Allow overriding environment settings for connect and read timeouts on URL connections. In milliseconds, 0 means infinite. |
|
22 |
|
|
Continue processing even after errors are encountered for run actions. Also used for some action to ignore certain errors like not found errors on remove actions. |
|
23 |
|
|
Name of file to restore and persist cookies across invocations of CLI actions. Can be used to provide Data Center session affinity for actions using REST APIs. |
|
24 |
|
|
Copy pattern for an artifact definition. |
|
25 |
|
|
Database name is required for SQL actions. |
|
26 |
|
|
Format string for dates in Java SimpleDateFormat. Default for output is client date format. Default for date parsing is lenient starting with client date format and then some other standard formats based on JSON date format. |
|
27 |
|
|
Alternate format string for dates in Java SimpleDateFormat. Use specific (may be ignored), but normally used for date only fields to avoid longer dateFormat based output. Some uses default to yyyy-MM-dd. |
|
28 |
|
|
Database table needs to be created before adding rows. |
|
29 |
|
|
By default, lib/jdbc is used to automatically load database drivers. Otherwise you can specify a specific file or url reference for the database driver jar. Example /jdbcDrivers/postgresql-9.3-1102.jdbc41.jar or https://jdbc.postgresql.org/download/postgresql-9.3-1102.jdbc41.jar
|
|
30 |
|
|
Database user password. Defaults to password. |
|
31 |
|
|
Database table name when creating or updating a database from list output. |
|
32 |
|
|
Comma separated list of column names used to access existing rows for update. Normally this defines a primary key set for the table. |
|
33 |
|
|
Database user name. Defaults to user. |
|
34 |
|
|
Requests detail debug output. Optional for all actions. |
|
35 |
|
|
Deployment project name or id. |
|
36 |
|
|
Description for entity. |
|
37 |
|
|
Disable an entity for those entities like plans, stages, jobs, and tasks. |
|
38 |
|
|
JDBC driver class or predefined value: postgresql, mysql, mssql, oracle, or db2400. Required for SQL actions. |
|
39 |
|
|
Enable an entity when updating. |
|
40 |
|
|
Character encoding (character set) for text based file content - must be an encoding supported by your JAVA platform. |
|
41 |
|
|
Deployment environment name or id. |
|
42 |
|
|
Event alias or key. Add-ons provide events identified by key. Example key: com.atlassian.bamboo.plugin.system.notifications:chainCompleted.failedChains |
|
43 |
|
|
Filter out entries that are disabled. |
|
44 |
|
|
Filter out entries that are enabled. |
|
45 |
|
|
Expanded request information to obtain more detailed data on request. |
|
46 |
|
|
Subset to favorites. Same as favourite. |
|
47 |
|
|
Subset to favourites. Same as favorite. |
|
48 |
|
|
Construct specific field or variable name. Value is specified by the value1 parameter. |
|
49 |
|
|
Construct specific field or variable name. Value is specified by the value2 parameter. |
|
50 |
|
|
Construct specific field or variable name. Value is specified by the value3 parameter. |
|
51 |
|
|
Construct specific field or variable name. Value is specified by the value4 parameter. |
|
52 |
|
|
Construct specific field or variable name. Value is specified by the value5 parameter. |
|
53 |
|
|
Construct specific field or variable name. Value is specified by the value6 parameter. |
|
54 |
|
|
Construct specific field or variable name. Value is specified by the value7 parameter. |
|
55 |
|
|
Construct specific field or variable name. Value is specified by the value8 parameter. |
|
56 |
|
|
Use to specify task or repository specific fields or variables and their values. A comma separated list of key:value pairs. Single quote the key:value pair if it contains a comma (,) or line breaks. |
|
57 |
f |
|
Path to file based content or result output. Use - for standard input. |
|
58 |
|
|
Make a final task. |
|
59 |
|
|
Find and replace text. Comma separated list of colon separated pairs. Single quote values containing a delimiter. Embedded quotes must be escaped. |
|
60 |
|
|
Find and replace text with a regular expression. Comma separated list of colon separated pairs. Single quote values containing a delimiter. Embedded quotes must be doubled. |
|
61 |
|
|
Prints this help message. |
|
62 |
|
|
Database host server for SQL actions. Not used if url is provided. Defaults to localhost if not provided. |
|
63 |
|
|
Stage or task id. |
|
64 |
|
|
Comma separated list of IP addresses to restrict ability to remotely trigger builds. |
|
65 |
|
|
Comma separated list of JIRA issue keys. |
|
66 |
|
|
Job key. Example: JOB1 |
|
67 |
|
|
Comma or blank separated list of labels. |
|
68 |
|
|
Maximum number of entries to return. |
|
69 |
|
|
Comma separated list of entries to populate the entry replacement variable on runFromList. Single quote values containing a delimiter. Embedded quotes must be doubled. |
|
70 |
|
|
Comma separated list of entries to populate the entry2 replacement variable on runFromList. Single quote values containing a delimiter. Embedded quotes must be doubled. |
|
71 |
|
|
Working directory relative path to a source location for an artifact definition or a destination location for an artifact dependency. |
|
72 |
|
|
Indicate that a stage be run manually. |
|
73 |
|
|
Name of entity, like plan name. |
|
74 |
|
|
Build number. Defaults to latest. |
|
75 |
|
|
Comma separated list of support, experimental, or other client or action specific options. |
|
76 |
|
|
Specify output format for an action. |
|
77 |
p |
|
User password for remote access. |
|
78 |
|
|
Plan key containing the project key. Preferred way to reference a plan instead of the older build terminology. Example: XXX-DEF |
|
79 |
|
|
Database host port for SQL actions. Optional, defaults to database default. Not used if url is provided. |
|
80 |
|
|
Project key. Example: XXX |
|
81 |
|
|
Project name. |
|
82 |
|
|
Property file with database parameters, field mappings, or client specific information. |
|
83 |
|
|
Limit some output messages. Optional for all actions. |
|
84 |
|
|
Recipient value for add notifications. Many recipient types need a primary recipient value. This parameter can be used instead of setting a recipient type specific field and value. |
|
85 |
|
|
Recipient type alias or key. Add-ons provide recipient types identified by key. Example key: com.atlassian.bamboo.plugins.bamboo-hipchat:recipient.hipchat |
|
86 |
|
|
Reference to a replacement key value used to remember an action specific value like issue key or similar so it can be referenced later.Each action that allows this parameter will specify what value is being set for the reference replacement key. |
|
87 |
|
|
Regular expression for list filtering and similar. Also for pattern match labelling. |
|
88 |
|
|
Replace existing entity on add, create, or similar actions. |
|
89 |
|
|
Name of a repository. In some cases, a comma separated list of repository names. |
|
90 |
|
|
Repository key that uniquely identifies the repository type. Example: com.atlassian.bamboo.plugins.atlassian-bamboo-plugin-mercurial:hg |
|
91 |
|
|
URL fragment for a request. |
|
92 |
|
|
URL request parameters or post data. |
|
93 |
|
|
Type of a render request like GET or POST |
|
94 |
|
|
Plan requirement key, either a custom key or a system capability key like: system.builder.ant.Ant. |
|
95 |
|
|
Revision id or tag. |
|
96 |
|
|
Cron, daily time, or periodic schedule. A cron schedule must be valid cron expresssions and defaults to 0 0 0 ? * *. A daily time is a 24 hour format (HH:mm) value. A periodic schedule is a numeric value in seconds and defaults to 180. |
|
97 |
|
|
Comma or blank separated list of labels used for search. |
|
98 |
s |
|
Server URL. Normally the base URL of the server and the same as how the server is accessed from a browser. |
|
99 |
|
|
Service address extension. |
|
100 |
|
|
For an artifact definition, makes the artifact available for other builds. |
|
101 |
|
|
Simulate running actions. Log the action that would be taken. |
|
102 |
|
|
Ordered list of alternate characters for comma ( , ), colon ( : ), at ( @ ), quote ( ' ), and double quote ( " ) characters used for specialized processing of some specific parameters. |
|
103 |
|
|
SQL select statement used to generate a run script. |
|
104 |
|
|
Stage name. |
|
105 |
|
|
Task id, name, or description. Task ids are unique, but names and descriptions are not. Name and description lookup is done by finding the first match in the ordered task list. |
|
106 |
|
|
Task key. Example: com.atlassian.bamboo.plugins.scripttask:task.builder.script.An alias can also be used to make it easier and less error prone. See addTask for the list. |
|
107 |
|
|
Wait timeout in seconds. Use -1 to wait forever. |
|
108 |
|
|
Plan key to be created. Example: XXX-DEF |
|
109 |
|
|
Project key to clone to. |
|
110 |
|
|
Requirement match type. Values: exist (default), equal, match. Also, content type for renderRequest and trigger type for addTrigger. |
|
111 |
|
|
Action specific setting. Example: Database access url for SQL actions. Optional when host is provided. |
|
112 |
u |
|
User name for remote access. |
|
113 |
|
|
Requirement match value. |
|
114 |
|
|
Value corresponding to the field1 parameter name. |
|
115 |
|
|
Value corresponding to the field2 parameter name. |
|
116 |
|
|
Value corresponding to the field3 parameter name. |
|
117 |
|
|
Value corresponding to the field4 parameter name. |
|
118 |
|
|
Value corresponding to the field5 parameter name. |
|
119 |
|
|
Value corresponding to the field6 parameter name. |
|
120 |
|
|
Value corresponding to the field7 parameter name. |
|
121 |
|
|
Value corresponding to the field8 parameter name. |
|
122 |
|
|
Requests verbose output to help with problem determination. Optional for all actions. |
|
123 |
|
|
Version name for deployment. |
|
124 |
|
|
Wait for action to complete. |
Log a request with our support team.
Confluence®, Jira®, Atlassian Bamboo®, Bitbucket®, Fisheye®, and Atlassian Crucible® are registered trademarks of Atlassian®
Copyright © 2005 - 2024 Appfire | All rights reserved. Appfire™, the 'Apps for makers™' slogan and Bob Swift Atlassian Apps™ are all trademarks of Appfire Technologies, LLC.