Parameters - 7.3.0

 

Parameter

Short

Value

Description

1

acceptType

 

Content type to accept for renderRequest if different than type.

2

accessKey

 

Secret access key for AWS credentials.

3

accessKeyId

 

Access key id for AWS credentials.

4

action

a

Requested operation to perform. Valid actions are listed at the end.

5

after

 

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.

6

afterSql

 

SQL to run after a successful action. Limited to specific actions at this time.

7

agent

 

Agent name.

8

append

 

 

Append to existing varaibles on updateVariables. For some actions using the file parameter, append will append output to the existing file.

9

artifact

 

Build artifact name. May be extended by a path name for locating files within an artifact representing a dirctory.

10

assignment

 

Key used to identify a project, plan, job, deployment proejct, or environment to be assigned to a specific agent. This makes the agent dedicated to only perform builds for all assignments. Examples: XXX, XXX-DEF, XXX-DEF-JOB1, Deployment for XXX-DEF, Deployment for XXX-DEF:QA, 77857004-77955436

11

automatic

 

 

Indicate that a stage be run automatically.

12

before

 

Before task name or id.

13

branch

 

Plan branch name normally. In the context of a repository it can reference a repository branch.

14

build

 

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

capability

 

Capability name (label) or key.

16

childPlans

 

Comma separated list of plan keys that represent child plan dependencies.

17

cleanAfter

 

 

Clean working directory after each job completes. Use on setJobOptions.

18

clearFileBeforeAppend

 

 

For run actions, this option will automatically clear an existing file on the first append requested.

19

columns

 

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.

20

comment

 

Comment text.

21

common

 

Common parameter string added to all run actions.

22

connectionTimeout

 

Allow overriding environment settings for connect and read timeouts on URL connections. In milliseconds, 0 means infinite.

23

continue

 

 

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.

24

cookies

 

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.

25

copyPattern

 

Copy pattern for an artifact definition.

26

credentials

 

Credentials name or id.

27

database

 

Database name is required for SQL actions.

28

dateFormat

 

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.

29

dateFormat2

 

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.

30

dbCreateTable

 

 

Database table needs to be created before adding rows.

31

dbJar

 

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

32

dbPassword

 

Database user password. Defaults to password.

33

dbTable

 

Database table name when creating or updating a database from list output.

34

dbTableKeys

 

Comma separated list of column names used to access existing rows for update. Normally this defines a primary key set for the table.

35

dbUser

 

Database user name. Defaults to user.

36

debug

 

 

Requests detail debug output. Optional for all actions.

37

deploymentProject

 

Deployment project name or id.

38

description

 

Description for entity.

39

disable

 

 

Disable an entity for those entities like plans, stages, jobs, and tasks.

40

driver

 

JDBC driver class or predefined value: postgresql, mysql, mssql, oracle, or db2400. Required for SQL actions.

41

enable

 

 

Enable an entity when updating.

42

encoding

 

Character encoding (character set) for text based file content - must be an encoding supported by your JAVA platform.

43

environment

 

Deployment environment name or id.

44

event

 

Event alias or key. Add-ons provide events identified by key. Example key: com.atlassian.bamboo.plugin.system.notifications:chainCompleted.failedChains

45

excludeDisabled

 

 

Filter out entries that are disabled.

46

excludeEnabled

 

 

Filter out entries that are enabled.

47

expand

 

Expanded request information to obtain more detailed data on request.

48

favorite

 

 

Subset to favorites. Same as favourite.

49

favourite

 

 

Subset to favourites. Same as favorite.

50

field

 

Use to set construct specific fields or variables using field=value syntax. The first equal sign (=) delineates the field name from it's value. Multiple field parameters can be provided. This provides a more convenient and expandable way to set fields as an alternative to the fields and numbered field parameters. Values are trimmed unless single quoted and single quoted strings will have single quotes removed.

51

field1

 

Construct specific field or variable name. Value is specified by the value1 parameter.

52

field2

 

Construct specific field or variable name. Value is specified by the value2 parameter.

53

field3

 

Construct specific field or variable name. Value is specified by the value3 parameter.

54

field4

 

Construct specific field or variable name. Value is specified by the value4 parameter.

55

field5

 

Construct specific field or variable name. Value is specified by the value5 parameter.

56

field6

 

Construct specific field or variable name. Value is specified by the value6 parameter.

57

field7

 

Construct specific field or variable name. Value is specified by the value7 parameter.

58

field8

 

Construct specific field or variable name. Value is specified by the value8 parameter.

59

fields

 

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.

60

file

f

Path to file based content or result output. Use - for standard input.

61

final

 

 

Make a final task.

62

findReplace

 

Find and replace text. Comma separated list of colon separated pairs. Single quote values containing a delimiter. Embedded quotes must be escaped.

63

findReplaceRegex

 

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.

64

help

 

 

Prints this help message.

65

host

 

Database host server for SQL actions. Not used if url is provided. Defaults to localhost if not provided.

66

id

 

Stage or task id.

67

ipRestriction

 

Comma separated list of IP addresses to restrict ability to remotely trigger builds.

68

issues

 

Comma separated list of JIRA issue keys.

69

job

 

Job key. Example: JOB1

70

labels

 

Comma or blank separated list of labels.

71

limit

 

Maximum number of entries to return.

72

list

 

Comma separated list of entries to populate the entry replacement variable on runFromList. Single quote values containing a delimiter. Embedded quotes must be doubled.

73

list2

 

Comma separated list of entries to populate the entry2 replacement variable on runFromList. Single quote values containing a delimiter. Embedded quotes must be doubled.

74

location

 

Working directory relative path to a source location for an artifact definition or a destination location for an artifact dependency.

75

manual

 

 

Indicate that a stage be run manually.

76

name

 

Name of entity, like plan name.

77

number

 

Build number. Defaults to latest.

78

options

 

Comma separated list of support, experimental, or other client or action specific options.

79

outputFormat

 

Specify output format for an action.

80

password

p

User password for remote access. This is a required parameter for most actions.

81

plan

 

Plan key containing the project key. Preferred way to reference a plan instead of the older build terminology. Example: XXX-DEF

82

port

 

Database host port for SQL actions. Optional, defaults to database default. Not used if url is provided.

83

project

 

Project key. Example: XXX

84

projectName

 

Project name.

85

propertyFile

 

Property file with database parameters, field mappings, or client specific information.

86

quiet

 

 

Limit some output messages. Optional for all actions.

87

recipient

 

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.

88

recipientType

 

Recipient type alias or key. Add-ons provide recipient types identified by key. Example key: com.atlassian.bamboo.plugins.bamboo-hipchat:recipient.hipchat

89

reference

 

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.

90

regex

 

Regular expression for list filtering and similar. Also for pattern match labelling.

91

replace

 

 

Replace existing entity on add, create, or similar actions.

92

repository

 

Name of a repository. In some cases, a comma separated list of repository names.

93

repositoryKey

 

Repository key that uniquely identifies the repository type. Example: com.atlassian.bamboo.plugins.atlassian-bamboo-plugin-mercurial:hg

94

request

 

URL fragment for a request.

95

requestParameters

 

URL request parameters or post data.

96

requestType

 

Type of a render request like GET or POST

97

requirement

 

Plan requirement key, either a custom key or a system capability key like: system.builder.ant.Ant.

98

revision

 

Revision id or tag.

99

schedule

 

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.

100

server

s

Server URL. Normally the same URL used when using a browser to access the server. This is a required parameter for most actions.

101

shared

 

 

For an artifact definition, makes the artifact available for other builds.

102

simulate

 

 

Simulate running actions. Log the action that would be taken.

103

special

 

Ordered list of alternate characters for comma ( , ), colon ( : ), at ( @ ), quote ( ' ), and double quote ( " ) characters used for specialized processing of some specific parameters.

104

sql

 

SQL select statement used to generate a run script.

105

sshParaphrase

 

Paraphrase for SSH credentials.

106

stage

 

Stage name.

107

successfulPlans

 

Comma separated list of keys that represent plans that must be successful before a build is triggered.

108

task

 

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.

109

taskKey

 

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.

110

timeout

 

Wait timeout in seconds. Use -1 to wait forever.

111

toPlan

 

Plan key to be created. Example: XXX-DEF

112

toProject

 

Project key to clone to.

113

triggeringEnvironment

 

Deployment environment name or id.

114

type

 

Capability type like Executable, Custom, or JDK.Also requirement match type with values: exist (default), equal, match. Also, content type for renderRequest and trigger type for addTrigger.

115

url

 

Action specific setting. Example: Database access url for SQL actions. Optional when host is provided.

116

user

u

User name for remote access.

117

userId

 

User id for user credentials.

118

userPassword

 

User password for user credentials.

119

value

 

Capability value or path. Also, requirement match value.

120

value1

 

Value corresponding to the field1 parameter name.

121

value2

 

Value corresponding to the field2 parameter name.

122

value3

 

Value corresponding to the field3 parameter name.

123

value4

 

Value corresponding to the field4 parameter name.

124

value5

 

Value corresponding to the field5 parameter name.

125

value6

 

Value corresponding to the field6 parameter name.

126

value7

 

Value corresponding to the field7 parameter name.

127

value8

 

Value corresponding to the field8 parameter name.

128

verbose

 

 

Requests verbose output to help with problem determination. Optional for all actions.

129

version

 

Version name for deployment.

130

wait

 

 

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.