Usage:
  bamboo (-a|--action) <action> [(-f|--file) <file>] [--encoding <encoding>] [--debug] [-v|--verbose] [--quiet] [--outputFormat
  <outputFormat>] [--columns <columns>] [--connectionTimeout <connectionTimeout>] [--sql <sql>] [--driver <driver>] [--url <url>]
  [--host <host>] [--port <port>] [--database <database>] [--dbUser <dbUser>] [--dbPassword <dbPassword>] [--dbJar <dbJar>]
  [--afterSql <afterSql>] [--dbTable <dbTable>] [--dbTableKeys <dbTableKeys>] [--dbCreateTable] [--comment <comment>] [--replace]
  [--propertyFile
  <propertyFile>] [--common <common>] [--special <special>] [--dateFormat <dateFormat>] [--dateFormat2 <dateFormat2>]
  [--reference
  <reference>] [--findReplace <findReplace>] [--findReplaceRegex <findReplaceRegex>] [--list <list>] [--list2 <list2>]
  [--options <options>] [--continue]
  [--simulate] [--append] [--clearFileBeforeAppend] (-s|--server) <server> (-u|--user) <user>
  (-p|--password) <password> [--serviceapi   <service><api>] [--apiservice <api><service>] [--cookies <cookies>] [--project <project>] [--toProject <toProject>]
  [--projectName <projectName>] [--deploymentProject <deploymentProject>] [--environment <environment>] [--version <version>] [--build
  <build>] [--plan <plan>] [--toPlan <toPlan>] [--stage <stage>] [--job <job>] [--task <task>] [--branch <branch>] [--name <name>]
  [--description <description>]   [--agent <agent>] [--assignment <assignment>] [--artifact <artifact>] [--requirement <requirement>]
  [--type <type>] [--value
  <value>] [--labels <labels>] [--searchLabels <searchLabels>] [--issues <issues>] [--expand <expand>]
  [--attribute <attribute>]
  [--comment <comment>] [--revision <revision>] [--location <location>] [--copyPattern <copyPattern>] [--repository <repository>]
  [--after <after>] [--schedule <schedule>] [--taskKey <taskKey>] [--repositoryKey <repositoryKey>] [--event <event>] [--recipientType <recipientType>]
 <recipientType>] [--recipient <recipient>] [--childPlans <childPlans>] [--ipRestriction <ipRestriction>] [--fields <fields>] [--field1 <field1>]
  [--field2
  <field2>] [--field3 <field3>] [--field4 <field4>] [--field5 <field5>] [--field6 <field6>] [--field7 <field7>] [--field8
  <field8>]
  [--value1 <value1>] [--value2 <value2>] [--value3 <value3>] [--value4 <value4>] [--value5 <value5>] [--value6 <value6>]
  [--value7
  <value7>] [--value8 <value8>] [--after <after>] [--before <before>] [--final] [--regex <regex>] [--request <request>]
  [--requestParameters <requestParameters>] [--requestType   <requestType>] [--acceptType <acceptType>] [--id <id>] [--number <number>]
  [--timeout <timeout>] [--limit <limit>] [--wait]
  [--favourite] [--favorite] [--enable] [--disable] [--excludeEnabled]
  [--excludeDisabled] [--manual] [--automatic] [--shared] [--cleanAfter]   [--help]


	Provides capability to make requests to a remote server.
	Required parameters: action, server, password.
	Optional parameters: user (likely required for your installation).
	Other required and optional parameters depending on action requested.


  (-a|--action) <action>
        Requested operation to perform. Valid actions are listed at the end.

  [(-f|--file) <file>]
        Path to file based content or result output. Use - for standard input.

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

  [--debug]
        Requests detail debug output. Optional for all actions.

  [-v|--verbose]
        Requests verbose output to help with problem determination. Optional for all actions.

  [--quiet]
        Limit some output messages. Optional for all actions.

  [--outputFormat <outputFormat>]
        Specify output format for an action. (default: 1)

  [--columns <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.

  [--connectionTimeout <connectionTimeout>]
        Allow overriding environment settings for connect and read timeouts on URL connections. In milliseconds, 0 means infinite.

  [--sql <sql>]
        SQL select statement used to generate a run script.

  [--driver <driver>]
        JDBC driver class or predefined value: postgresql, mysql, mssql, oracle, or db2400. Required for SQL actions.

  [--url <url>]
        Action specific setting. Example: Database access url for SQL actions. Optional when host is provided.

  [--host <host>]
        Database host server for SQL actions. Not used if url is provided. Defaults to localhost if not provided.

  [--port <port>]
        Database host port for SQL actions. Optional, defaults to database default. Not used if url is provided.

  [--database <database>]
        Database name is required for SQL actions.

  [--dbUser <dbUser>]
        Database user name. Defaults to user.

  [--dbPassword <dbPassword>]
        Database user password. Defaults to password.

  [--dbJar <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

  [--afterSql <afterSql>]
        Experimental. SQL to run after a successful action. Limited to specific actions at this time.

  [--dbTable <dbTable>]

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

  [--dbTableKeys <dbTableKeys>]

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

  [--dbCreateTable]

       Experimental. Database table needs to be created before adding rows.

  [--comment <comment>]
        Comment text.

  [--replace]
        Replace existing entity on add, create, or similar actions.

  [--propertyFile <propertyFile>]
        Property file with database parameters, field mappings, or client specific information.

  [--common <common>]
        Common parameter string added to all run actions.

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

  [--dateFormat <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.

  [--dateFormat2 <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.

  [--reference <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.

  [--findReplace <findReplace>]
        Find and replace text. Comma separated list of colon separated pairs. Single quote values containing a delimiter. Embedded
        quotes must be escaped.

  [--findReplaceRegex <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.

  [--list <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.

  [--list2 <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.

  [--continueoptions <options>]
        ContinueComma processingseparated evenlist afterof errorssupport, areexperimental, encountered or other client or action specific options.

  [--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.

  [--simulate]
        Simulate running actions. Log the action that would be taken.

  [--append]
        For some actions using the file parameter, append will append output to the existing file.

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

  (-s|--server) <server>
        Server URL. Normally the base URL of the server and the same as how the server is accessed from a browser.

  (-u|--user) <user>
        User name for remote access. (default: automation)

  (-p|--password) <password>
        User password for remote access.

  [--serviceapi <service><api>]
        ServiceAPI addressversion. extension. (default: /rest/api)

  [--api <api>]
        API version. Some requests produce different results based on the api version usedSome requests produce different results based on the api version used. (default: latest)

  [--service <service>]
        Service address extension. (default: latest/rest/api)

  [--cookies <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.

  [--project <project>]
        Project key. Example: XXX

  [--toProject <toProject>]
        Project key to clone to.

  [--projectName <projectName>]
        Project name.

  [--builddeploymentProject <build><deploymentProject>]
        BuildDeployment key. project name or id.

  [--environment <environment>]
        Deployment environment name or id.

  [--version <version>]
        Version name for deployment.

  [--build <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

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

  [--toPlan <toPlan>]
        Plan key to be created. Example: XXX-DEF

  [--stage <stage>]
        Stage name.

  [--job <job>]
        Job key. Example: JOB1

  [--nametask <name><task>]
        NameTask ofid, entityname, likeor plan namedescription. Task ids  [--description <description>]
        are unique, but names and descriptions are not. Name and description lookup is done
        by finding the first match in the ordered task list.

  [--branch <branch>]
        Branch name.

  [--name <name>]
        Name of entity, like plan name.

  [--description <description>]
        Description for entity.

  [--agent <agent>]
        Agent name.

  [--assignment <assignment>]
        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

  [--artifact <artifact>]
        Build artifact name. May be extended by a path name for locating files within an artifact representing a dirctory.

  [--requirement <requirement>]
        Plan requirement key, either a custom key or a system capability key like: system.builder.ant.Ant.

  [--type <type>]
        Requirement match type. Values: exist (default), equal, match. Also, content type for renderRequest and trigger type for
        addTrigger. (default: )

  [--value <value>]
        Requirement match value.

  [--labels <labels>]
        Comma or blank separated list of labels.

  [--searchLabels <searchLabels>]
        Comma or blank separated list of labels used for search.

  [--issues <issues>]
        Comma separated list of JIRA issue keys.

  [--expand <expand>]
        Expanded request information to obtain more detailed data on request.

  [--attribute <attribute>]
        Attribute to list.

  [--commentrevision <comment><revision>]
        Comment for an build.

  [--revision <revision>]
        Revision Revision id or tag.

  [--location <location>]
        Working directory relative path to a source location for an artifact definition or a destination location for an artifact
        dependency.

  [--copyPattern <copyPattern>]
        Copy pattern for an artifact definition.

  [--repository <repository>]
        Name of a repository. In some cases, a comma separated list of repository names.

  [--after <after>]
        Used in orderRepository to name the repository after which the repository will be positioned.

  [--schedule <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.

  [--taskKey <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.

  [--repositoryKey <repositoryKey>]
        Repository key that uniquely identifies the repository type. Example:
        com.atlassian.bamboo.plugins.atlassian-bamboo-plugin-mercurial:hg

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

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

  [--childPlansrecipient <childPlans><recipient>]
        CommaRecipient separatedvalue listfor ofadd plannotifications. keysMany thatrecipient representtypes childneed plana dependencies.primary recipient value. This [--ipRestriction <ipRestriction>]
 parameter can be used
      Comma separated listinstead of setting a recipient type specific field and value.

  [--childPlans <childPlans>]
        Comma separated list of plan keys that represent child plan dependencies.

  [--ipRestriction <ipRestriction>]
        Comma separated list of IP addresses to restrict ability to remotely trigger builds.

  [--fields <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.

  [--field1 <field1>]
        Construct specific field or variable name. Value is specified by the value1 parameter.

  [--field2 <field2>]
        Construct specific field or variable name. Value is specified by the value2 parameter.

  [--field3 <field3>]
        Construct specific field or variable name. Value is specified by the value3 parameter.

  [--field4 <field4>]
        Construct specific field or variable name. Value is specified by the value4 parameter.

  [--field5 <field5>]
        Construct specific field or variable name. Value is specified by the value5 parameter.

  [--field6 <field6>]
        Construct specific field or variable name. Value is specified by the value6 parameter.

  [--field7 <field7>]
        Construct specific field or variable name. Value is specified by the value7 parameter.

  [--field8 <field8>]
        Construct specific field or variable name. Value is specified by the value8 parameter.

  [--value1 <value1>]
        Value corresponding to the field1 parameter name.

  [--value2 <value2>]
        Value corresponding to the field2 parameter name.

  [--value3 <value3>]
        Value corresponding to the field3 parameter name.

  [--value4 <value4>]
        Value corresponding to the field4 parameter name.

  [--value5 <value5>]
        Value corresponding to the field5 parameter name.

  [--value6 <value6>]
        Value corresponding to the field6 parameter name.

  [--value7 <value7>]
        Value corresponding to the field7 parameter name.

  [--value8 <value8>]
        Value corresponding to the field8 parameter name.

  [--regexafter <regex><after>]
        Regular expression for list filtering and similar. Also for pattern match labelling.

  [--request <request>]Used in orderRepository to name the repository after which the repository will be positioned. Similarly for moveTask where
        it represent URLthe fragmentid forof athe requesttask.

  [--requestParametersbefore <requestParameters><before>]
        URLBefore request parameters or post datatask id.

  [--requestType <requestType>final]
        TypeMake of a render request like GET or POST (default: GET)final task.

  [--acceptTyperegex <acceptType><regex>]
        Regular expression Contentfor typelist tofiltering acceptand forsimilar. renderRequestAlso iffor differentpattern thanmatch typelabelling.

  [--idrequest <id><request>]
        URL Stagefragment orfor taska idrequest.

  [--numberrequestParameters <number><requestParameters>]
        BuildURL number.request Defaultsparameters toor latest. (default: 0)post data.

  [--timeoutrequestType <timeout><requestType>]
        WaitType timeoutof ina seconds.render Userequest -1like toGET waitor forever.POST (default: -1GET)

  [--limitacceptType <limit><acceptType>]
        Content Maximumtype to numberaccept offor entriesrenderRequest toif return. (default: 2147483647)different than type.

  [--waitid <id>]
        WaitStage foror actiontask to completeid.

  [--favouritenumber <number>]
        SubsetBuild number. Defaults to favouriteslatest. Same as favorite.
(default: 0)

  [--favoritetimeout <timeout>]
        Wait Subsettimeout toin favoritesseconds. SameUse as favourite.-1 to wait forever. (default: -1)

  [--enablelimit <limit>]
        Maximum Enablenumber anof entityentries whento updatingreturn. (default: 2147483647)

  [--disablewait]
        Disable anWait entity for thoseaction entities like plans, stages, jobs, and tasksto complete.

  [--excludeEnabledfavourite]
        FilterSubset outto entriesfavourites. thatSame areas enabledfavorite.

  [--excludeDisabledfavorite]
        FilterSubset outto entriesfavorites. thatSame areas disabledfavourite.

  [--manualenable]
        IndicateEnable thatan aentity stage be run manuallywhen updating.

  [--shareddisable]
        ForDisable an artifactentity definition,for makesthose the artifact available for other buildsentities like plans, stages, jobs, and tasks.

  [--cleanAfterexcludeEnabled]
        CleanFilter workingout directoryentries afterthat each job completes. Use on setJobOptionsare enabled.

  [--helpexcludeDisabled]
        Filter Printsout entries thisthat helpare messagedisabled.

 Valid actions (case insensitive):

run - Run actions from a file or standard input.
	 Required parameters: file or standard input
	 Optional parameters: common, continue, simulate, clearFileBeforeAppend, encoding, findReplace, findReplaceRegex
runFromSql - Run actions generated by SQL provided by the sql parameter, a file, or standard input
	 Required parameters: sql or file or standard input
	 Optional parameters: common, driver, database, host, port, url, dbUser, dbPassword,
	 propertyFile, continue, simulate, clearFileBeforeAppend, encoding, findReplace, findReplaceRegex
runFromCsv - Run actions generated from a CSV file.
	 Required parameters: file
	  [--manual]
        Indicate that a stage be run manually.

  [--automatic]
        Indicate that a stage be run automatically.

  [--shared]
        For an artifact definition, makes the artifact available for other builds.

  [--cleanAfter]
        Clean working directory after each job completes. Use on setJobOptions.

  [--help]
        Prints this help message.


Valid actions (case insensitive):

run - Run actions from a file or standard input.
	 Required parameters: file or standard input
	 Optional parameters: common, propertyFile, continue, quiet, simulate, clearFileBeforeAppend, encoding, findReplace, findReplaceRegex
runFromListrunFromSql - Run actions generated forby eachSQL entryprovided inby athe list.sql 	parameter, Whena file, isor provided,standard eachinput
action	 inRequired theparameters: filesql augmentedor byfile theor commonstandard parameterinput
will	 beOptional runparameters: forcommon, each entry.
	 Otherwise, just the action specified by the common parameter will be run.
	 Available replacement variables are entry, entry2driver, database, host, port, url, dbUser, dbPassword,
	 propertyFile, continue, simulate, clearFileBeforeAppend, encoding, findReplace, findReplaceRegex
runFromCsv - Run actions generated from a CSV file.
	 Required parameters: listfile
	 Optional parameters: list2common, file, commonpropertyFile, continue, quiet, simulate, clearFileBeforeAppend, encoding, findReplace, findReplaceRegex
getClientInforunFromList - Run Getactions informationfor abouteach theentry thisin clienta toollist.
	 OptionalWhen parameters:file outputFormat,is fileprovided, append,each encodingaction 	in Outputthe formats:file 1augmented -by basic,the 2common -parameter JVMwill getServerInfo be run for each entry.
	 Otherwise, just the action specified by the common parameter will be run.
	 Available replacement variables are entry, entry2.
	 Required parameters: list
	 Optional parameters: list2, file, common, continue, quiet, simulate, clearFileBeforeAppend, encoding, findReplace, findReplaceRegex
getClientInfo - Get information about the Bamboothis client servertool.
	 Optional parameters: outputFormat, dateFormat, file, append, encoding
	 Output formats: 1 - basic, 2 - detailJVM, 311 - action statelist, validateLicense12 - Validates parameter list
getServerInfo - Get information about the Bamboo server.
	 Optional parameters: outputFormat, dateFormat, file, append, encoding
	 Output formats: 1 - basic, 2 - detail, 3 - state
validateLicense - Validates the CLI Connector is enabled and licensed on the server.
renderRequest - Render url based request. The response data modified by findReplace processing is returned.
	 Required parameters: request
	 Optional parameters: requestParameters, requestType, type, acceptType, build, file, encoding, findReplace, findReplaceRegex
runFromProjectList - Run actions for each project with regex filtering on project key or name. Available replacement variables are project and projectName.
	 Optional parameters: regex, common, continue, simulate, clearFileBeforeAppend, file, encoding, findReplace, findReplaceRegex
runFromPlanList - Run actions for each plan with regex filtering on plan key or name. Use @all for project to get a list of plans across all projects. Available replacement variables are project, projectName, plan, and planName.
	 Required parameters: project
	 Optional parameters: favorite, excludeDisabled, excludeEnabled, regex, common, continue, simulate, clearFileBeforeAppend, file, encoding, findReplace, findReplaceRegex
runFromStageList - Run actions for each stage with regex filtering on stage name. Available replacement variables are project, projectName, plan, planName, stageId, and stageName.
	 Required parameters: plan
	 Optional parameters: stage, regex, common, continue, simulate, clearFileBeforeAppend, file, encoding, findReplace, findReplaceRegex
runFromJobList - Run actions for each job with regex filtering on job key or name. Restrict to a specific stage or leave stage blank to get jobs across all stages. Available replacement variables are project, projectName, plan, planName, stageId, stageName, job, and jobName.
	 Required parameters: plan
	 Optional parameters: stage, regex, common, continue, simulate, clearFileBeforeAppend, file, encoding, findReplace, findReplaceRegex
runFromRepositoryList - Run actions for each repository with regex filtering on repository name. Available replacement variables are repository and repositoryId.
	 Optional parameters: plan, regex, common, continue, simulate, clearFileBeforeAppend, file, encoding, findReplace, findReplaceRegex
runFromAgentList - Run actions for each agent with regex filtering on agent name. Available replacement variables are agent and agentId.
	 Optional parameters: regex, common, continue, simulate, clearFileBeforeAppend, file, encoding, findReplace, findReplaceRegex
getProjectListrunFromDeploymentProjectList - GetExperimental. aRun listactions offor projects.each Projectsdeployment are selected based onproject with regex filtering on deployment project key or name name. Available replacement variables are deploymentProject and deploymentProjectId.
	 Optional parameters: regex, filecommon, appendcontinue, encodingsimulate, columns
getPlanListclearFileBeforeAppend, file, encoding, findReplace, findReplaceRegex
runFromEnvironmentList - Get a list of plansExperimental. Run actions for each environment defined for a deployment project with regex filtering on plan key orenvironment name. UseAvailable @allreplacement forvariables projectare toenvironment get a list of plans across all projects.
	 Required parameters: projectand environmentId.
	 Optional parameters: favoriteregex, excludeDisabledcommon, excludeEnabledcontinue, limitsimulate, regexclearFileBeforeAppend, outputFormatfile, dateFormatencoding, columnsfindReplace, file,findReplaceRegex
append,getProjectList encoding- 	Get Outputa formats:list 1of -projects. plan,Projects 999are -selected lastbased buildon resultsregex filtering getArtifactDefinitionListon -project Experimentalkey -or onlyname.
those	 availableOptional toparameters: beregex, artifactfile, dependenciesappend, inencoding, thecolumns
lastgetPlanList job!- Get a list of shared artifact definitionsplans for a planproject with regex filtering on plan key artifactor name. Use @all for project to get a list of plans across all projects.
	 Required parameters: planproject
	 Optional parameters: favorite, excludeDisabled, excludeEnabled, limit, regex, outputFormat, dateFormat, columns, file, append, encoding
getRepositoryList	 -Output Getformats: a1 list- ofplan, global999 or- planlast repositoriesbuild with results
getBranchList - Get a list of branches for a plan with regex filtering on repository branch name or short name.
	 Required parameters: plan
	 Optional parameters: planlimit, regex, columns, file, append, encoding
getNotificationListgetArtifactDefinitionList - Get a EAPlist (subjectof toartifact change).definitions Getfor a list of plan notifications plan with regex filtering on artifact name.
	 Required parameters: plan
	 Optional parameters: plan limit, regex, columns, file, append, encoding
getVariableListgetRepositoryList - Get a list of global or plan variablesrepositories basedwith on regex filtering ofon variablerepository namesname.
	 Optional parameters: plan, regex, file, append, encoding
getBuildListgetNotificationList - Get a list of buildplan reultsnotifications.
Build	 resultsOptional can parameters: plan, file, append, encoding
getVariableList - Get a list of global or plan variables based on regex filtering of variable names.
	 Optional parameters: plan, regex, file, append, encoding
getBuildList - Get a list of build reults. Build results can be filtered by using fields and values. Supported fields are state, notState, and started. For example, include only successful results by using: --field1 state --value SUCCESSFUL, or include only builds started after a specific date use: --field2 started --value2 2016-04-30 --dateFormat yyyy-MM-dd. Default limit is 25.
	 Required parameters: plan
	 Optional parameters: limit, favorite, labels, issues, columns, file, append, encoding, fields, field1, value1, field2, value2, field3, value3, field4, value4, field5, value5, field6, value6, field7, value7, field8, value8
	 Output formats: 1 - basic, 2 - test information
getArtifactList - Get a list of build result artifacts. When the build does not include a job portion, only shared artifacts are provided. Use @all for the job parameter to get both sharted and non-shared artifacts for all plan jobs.
	 Required parameters: plan or build
	 Optional parameters: job, number, limit, regex, file, append, encoding
getBuildQueueList - Get a list of builds waiting in the build queue. Subset by project or build.
	 Optional parameters: project, build, file, append, encoding, columns
getLabelList - Get a list of labels for a build.
	 Required parameters: build
	 Optional parameters: number, file, append, encoding, columns
getCommentList - Get a list of comments for a build.
	 Required parameters: build
	 Optional parameters: number, file, append, encoding, columns
getStageList - Get a list of stages for a plan with regex filtering on stage name.
	 Required parameters: plan
	 Optional parameters: regex, file, attribute, columns
getJobList - Get a list of jobs for a plan with regex filtering on job key or name. Subset by stage if desired.
	 Required parameters: plan
	 Optional parameters: stage, regex, file, attribute, columns
getAgentListgetTaskList - Get a list of tasks for agentsa basedjob onwith regex filtering ofon agenttask names.name.
	 OptionalRequired parameters: regexplan, file,job
append, encoding	 Optional parameters: limit, columnsregex, 	file, Outputcolumns
formats:getAgentList 1- -Get basic,a 2list -of detailagents queueBuildbased -on Queueregex afiltering buildof toagent runnames.
	 IfOptional waitparameters: isregex, specifiedfile, theappend, actionencoding, willcolumns
not	 completeOutput untilformats: the1 queued- buildbasic, completes2 or- thedetail
timeoutgetDeploymentProjectList period- elapsesExperimental. TheGet actiona willlist failof ifdeployment theprojects buildbased failson unlessregex continuefiltering parameterof isproject usednames.
to	 ignoreOptional aparameters: failed result. A specific revision can be built if the revision parameter is specified. Plan variables can be set using the field and value parameters. Conditional queueing is supported - see the documentation for detailsregex, file, append, encoding, columns
getEnvironmentList - Experimental. Get a list of environments for a deployment project based on regex filtering of environment names.
	 Required parameters: plandeploymentProject
	 Optional parameters: revisionregex, waitfile, continueappend, timeoutencoding, dateFormat,columns
fields,getTaskTypeList field1,- value1,Get field2,a value2,list field3,of value3,task field4,types value4,available field5,with value5,regex field6,filtering value6,on field7,type value7,name field8,and value8description.
queueBuildFromList	 -Required Queueparameters: multipleplan, buildsjob
to	 runOptional andparameters: waitlimit, for results. The action will not complete until all queued builds complete or times out. If continue is specified, builds will continue to be queued even after an attempt to queue a build fails. Theregex, file, columns
pauseServer - Pause the server to prevent builds from starting.
resumeServer - Resume server to allow builds to be started.
queueBuild - Queue a build to run. If wait is specified, the action will failnot if any build fails or times outcomplete until the queued build completes or the timeout period elapses. The action will fail if the build fails unless continue parameter is used to ignore a failed result. A specific revision can be built if the revision parameter is specified. Plan variables can be set using the field and value parameters. Conditional queueing is supported - see the documentation for details.
	 Required parameters: project orplan
list
	 Optional parameters: branch, regexrevision, limitwait, continue, timeout, dateFormat, fields, field1, value1, field2, value2, field3, value3, field4, value4, field5, value5, field6, value6, field7, value7, field8, value8
stopBuildqueueBuildFromList - RequestQueue multiple builds to stop arun and wait for results. The action will not complete until all queued builds complete or runningtimes build. Useout. If continue is specified, builds will continue to be ignorequeued errorseven findingafter aan buildattempt to stopqueue ora failedbuild resultsfails. The wait parameter will cause processing to wait for completion or timeout before returning action will fail if any build fails or times out. Conditional queueing is supported - see the documentation for details.
	 Required parameters: project or planlist
	 Optional parameters: waitregex, timeoutlimit, continue, restartBuild - Restart a build that failed or was stoppedtimeout, dateFormat, fields, field1, value1, field2, value2, field3, value3, field4, value4, field5, value5, field6, value6, field7, value7, field8, value8
stopBuild - Request to stop a queued or running build. Use continue to ignore errors finding a build to restartstop or failed results. The wait parameter will cause processing to wait for completion or timeout before returning.
	 Required parameters: plan
	 Optional parameters: wait, timeout, continue
addCommentrestartBuild - AddRestart a build that commentfailed toor awas buildstopped. 	Use Required parameters:continue to ignore errors finding a build to restart or failed results.
	 Required parameters: plan
	 Optional parameters: wait, timeout, continue
addComment - Add a comment to a build.
	 Required parameters: build, comment
	 Optional parameters: number, findReplace, findReplaceRegex, file, encoding
addLabels - Add a comma separated list of labels to a build.
	 Required parameters: build, labels
	 Optional parameters: number
removeLabels - Remove labels from a build. Labels can be a comma separated list or regex. Either build or search terms (searchLabels, issues) must be provided
	 Required parameters: labels
	 Optional parameters: build, number, searchLabels, issues, favorite
deleteProject - Delete project and all project plans.
	 Required parameters: project
	 Optional parameters: file
enableProject - Enable all project plans.
	 Required parameters: project
disableProject - Disable all project plans.
	 Required parameters: project
cloneProject - Clone each plan in a project to another project. If toProject is not provided, the plans will be cloned to the same project. If the toProject does not exist, it will be created with name provided by projectName.
	 Required parameters: project, toProject, projectName, disable
createPlan - Create a new plan. Provide a 2-part plan key where the first part is the project key. If the project key does not exist, it will be created with the provided project name. Server instances only. Use continue to ignore the request if the plan already exists.
	 Required parameters: plan
	 Optional parameters: name, projectName, description, disable, continue
createOrUpdatePlan - Same as createPlan when plan does not exist. However, it will update an existing plan's name and description.
Server instances only.
	 Required parameters: plan
	 Optional parameters: name, projectName, description, disable
updatePlan - Update a plans name or description. Provide a 2-part plan key where the first part is the project key.
	 Required parameters: plan
	 Optional parameters: name, description
getPlan - Get plan information.
	 Required parameters: plan
clonePlan - Clone a plan.
	 Required parameters: plan, toPlan, name
	 Optional parameters: description, projectName, disable
deletePlan - Delete a plan.
	 Required parameters: plan
enablePlan - Enable a plan to run.
	 Required parameters: plan
disablePlan - Disable a plan from running.
	 Required parameters: plan
addStagesetFavoritePlan - AddSet athe stageplan toas a planfavorite.
	 Required parameters: plan,
stageunsetFavoritePlan 	- OptionalRemove parameters:the description,plan manualfrom removeStagethe -favorite Removelist.
a	 stage from aRequired parameters: plan.
Use id =exportPlan -1 toExperimental. removeExport alla stages. Use continue plan to ignoresource notthat foundcan errors.be 	 Required parameters:used for plan, stagecreation. or idValid 	export Optionaltypes parameters:are continueCLI, addJobJAVA - Add a job to a stage(Bamboo 6.0 and higher).
	 Required parameters: plan, stage,
job
	 Optional parameters: type, namefile, descriptionencoding, disabledateFormat
enableJobmovePlans - EnableMove aone jobor tomore run.plans 	from Requiredone parameters:project plan,to jobanother disableJob - Disableproject (existing or new). Specifying a jobplan fromwill running.move 	that Requiredplan. parameters:If plan, is jobnot setJobOptionsspecified, -plans Setfrom miscellaneousthe optionsource forproject, awith job.filtering Thelike followingfor optionsgetPlanList, arewill specificallybe supported:moved. cleanPlan workingkey directoryand aftername jobcan completesbe (cleanAfterchanged switch)on andthe patternmove matchingby labelingspecifying (regextoPlan and labelsname parameters)respectively. UseWhen thetoPlan fieldor andname valueare parametersprovided for additionalmultiple settingsplan withmoves, valuesthey determined from the screen. Some previous settings may be lost if not specifically requestedmust contain <at:var at:name="plan" /> or <at:var at:name="planName" /> replacement variables. Before the move takes place, the server state will be checked and paused if necessary and, if paused, resumed after the end of the operation.
	 Required parameters: project or plan, jobtoProject
	 Optional parameters: cleanAftertoPlan, regexname, labelsexcludeEnabled, getArtifactexcludeDisabled, -limit, Downloadregex
aaddBranch copy- ofAdd a buildbranch artifactto into a fileplan. 	The Requiredplan parameters:branch will Usesbe samedisabled parametersby anddefault. logicFor asadd, getArtifactListthe forbranch identifyingparameter buildrefers resultto artifactsthe torepository searchbranch. ForAn optional artifactsname thatfor representthe aplan directorybranch (notcan abe file)specified, useotherwise the repository artifactbranch name pluswill the path to the file in the artifactbe used.
	 OptionalRequired parameters: plan or build, artifact, filebranch
	 OutputOptional formatsparameters: jobname, numberdescription, replace, encoding
getBuildenable
removeBranch - GetRemoves builda result.branch 	from Requireda parameters:plan. buildUse 	--branch Optional@all parameters:to number,remove expand,all filebranches verifyBuildfrom - Verify build was successfula plan.
	 Required parameters: build
	 Optional parameters: number
getLatestBuildNumber - Get the number of the last completed build for this plan plan, branch
getBranch - Get information for a branch to a plan. Branch can be either the short or long name of the branch.
	 Required parameters: plan, addArtifact - Add an artifact definition to a job. Server instances onlybranch
	 Optional parameters: file, encoding
addStage - Add a stage to a plan.
	 Required parameters: plan, job, artifact, copyPattern
stage
	 Optional parameters: locationdescription, sharedmanual
removeArtifactgetStage - Remove an artifact definition from a job. Server instances only Get plan stage information.
	 Required parameters: plan, stage
updateStage - Update stage details.
	 Required parameters: plan, job,stage
artifact	 addArtifactDependencyOptional -parameters: Addname, andescription, artifactmanual, dependencyautomatic
toremoveStage a job. Artifact must be- Remove a shared artifactstage from anothera jobplan. 	Use Required parameters: plan, job, artifact, location
setDependencyOptions - Experimental. Set child dependencies and other related options--stage @all to remove all stages. Use continue to ignore not found errors.
	 Required parameters: plan, 	 stage or id
	 Optional parameters: children, fields, field1, value1, field2, value2, field3, value3, field4, value4, field5, value5, field6, value6, field7, value7, field8, value8
addTask - Add a task to a plan job. A valid task key or alias is required. Valid aliases are: ANT, ARTIFACT_DOWNLOAD, CHECKOUT, CLI_BAMBOO, CLI_CONFLUENCE, CLI_CRUCIBLE, CLI_FISHEYE, CLI_HIPCHAT, CLI_JIRA, CLI_SERVICE_DESK, CLI_STASH, CLI_UPM, GANT, GINT, GRADLE, GRADLEW, GROOVY, MAVEN2, MAVEN3, SCP, SQL, SCRIPT, SSH, VARIABLE_REPLACE
	 Required parameters: plan, job, taskKey
	 Optional parameters: disable, fields, field1, value1, field2, value2, field3, value3, field4, value4, field5, value5, field6, value6, field7, value7, field8, value8
updateTask - Update a task in a plan job. You must provide the same parameters as if you were creating the task continue
addJob - Add a job to a stage.
	 Required parameters: plan, stage, job
	 Optional parameters: name, description, disable
enableJob - Enable a job to run.
	 Required parameters: plan, job
disableJob - Disable a job from running.
	 Required parameters: plan, job
setJobOptions - Set miscellaneous option for a job. The following options are specifically supported: clean working directory after job completes (cleanAfter switch) and pattern matching labeling (regex and labels parameters). Use the field and value parameters for additional settings with values determined from the screen. Some previous settings may be lost if not specifically requested.
	 Required parameters: plan, job
	 Optional parameters: cleanAfter, regex, labels
getArtifact - Download a copy of a build artifact into a file.
	 Required parameters:  Uses same parameters and logic as getArtifactList for identifying build result artifacts to search. For artifacts that represent a directory (not a file), use the artifact name plus the path to the file in the artifact.
	 Optional parameters: plan or build, artifact, file
	 Output formats: job, number, replace, encoding
getBuild - Get build result.
	 Required parameters: build
	 Optional parameters: number, expand, file, encoding
verifyBuild - Verify build was successful.
	 Required parameters: build
	 Optional parameters: number
getLatestBuildNumber - Get the number of the last completed build for this plan.
	 Required parameters: plan
addArtifact - Add an artifact definition to a job.
	 Required parameters: plan, job, artifact, copyPattern
	 Optional parameters: location, shared
removeArtifact - Remove an artifact definition from a job.
	 Required parameters: plan, job, artifact
addArtifactDependency - Add an artifact dependency to a job. Artifact must be a shared artifact from another job.
	 Required parameters: plan, job, artifact, location
setDependencyOptions - Set child dependencies and other related options.
	 Required parameters: plan
	 Optional parameters: children, fields, field1, value1, field2, value2, field3, value3, field4, value4, field5, value5, field6, value6, field7, value7, field8, value8
addTask - Add a task to a plan job. A valid task key or alias is required. Valid aliases are: ANT, ARTIFACT_DOWNLOAD, CHECKOUT, CLI_BAMBOO, CLI_BITBUCKET, CLI_CONFLUENCE, CLI_CRUCIBLE, CLI_FISHEYE, CLI_HIPCHAT, CLI_JIRA, CLI_SERVICE_DESK, CLI_UPM, GANT, GINT, GRADLE, GRADLEW, GROOVY, MAVEN2, MAVEN3, SCP, SQL, SCRIPT, SSH, VARIABLE_REPLACE
	 Required parameters: plan, job, taskKey
	 Optional parameters: disable, final, fields, field1, value1, field2, value2, field3, value3, field4, value4, field5, value5, field6, value6, field7, value7, field8, value8
updateTask - Update a task in a plan job. You must provide the same parameters as if you were creating the task.
	 Required parameters: plan, job, task or id
	 Optional parameters: enable, disable, fields, field1, value1, field2, value2, field3, value3, field4, value4, field5, value5, field6, value6, field7, value7, field8, value8
removeTask - Remove a task from a plan job. Use --task @all to remove all tasks.
	 Required parameters: plan, job, task or id
moveTask - Move a task to before or after another task. Use final to make a task final. Final tasks must follow all non final tasks. If neither before or after are specified, the task will be moved to the last position respecting the final parameter.
	 Required parameters: plan, job, task or id
	 Optional parameters: after or before, final
getTask - Get detail information on a task from a plan job. Use --task @all to give detail information on all tasks for a job.
	 Required parameters: plan, job, task or id
addRepository - Add a global or plan repository. For a plan repository, you can reference a linked (global) repository. Otherwise a valid repository key or alias is required. Valid aliases are: BITBUCKET, BITBUCKET_CLOUD, BITBUCKET_SERVER, STASH, BCVS, GIT, GITHUB, MERCURIAL, PERFORCE, SUBVERSION
	 Required parameters: repository or name
	 Optional parameters: plan, repositoryKey, replace, fields, field1, value1, field2, value2, field3, value3, field4, value4, field5, value5, field6, value6, field7, value7, field8, value8
updateRepository - Update a global or plan repository.
	 Required parameters: repository or id
	 Optional parameters: plan, fields, field1, value1, field2, value2, field3, value3, field4, value4, field5, value5, field6, value6, field7, value7, field8, value8
removeRepository - Remove global or plan repository. Use @all to remove all repositories.
	 Required parameters: repository or id
	 Optional parameters: plan, continue
getRepository - Get details of a global or plan repository. Sets the repository and repositoryId replacement variables.
	 Required parameters: repository
	 Optional parameters: plan
orderRepository - Order repository in the list of repositories for a plan. Defaults to move the repository to the top to make it the default repository. Otherwise specify the after respository name.
	 Required parameters: plan, repository
	 Optional parameters: after
addRequirement - Add requirement to a plan job.
	 Required parameters: plan, job, requirement
	 Optional parameters: type, value
updateRequirement - Update a plan requirement.
	 Required parameters: plan, job, id
	 Optional parameters: enabletype, disable,value
fields,removeRequirement field1,- value1,Remove field2,a value2, field3, value3, field4, value4, field5, value5, field6, value6, field7, value7, field8, value8
removeTask - Remove a task fromplan requirement.
	 Required parameters: plan, job, id
addNotification - Add a plan jobnotification. UseThere idare =2 -1parts to a removenotification all- tasks.an 	event Requiredthat parameters:triggers plan,the job,notification idand addRepositorya -recipient Addtype athat globaldetermines orthe plannotification repositoryprotocol. For a plan repository, you can reference a linked (global) repository. Otherwise a valid repository key or alias is required. Valid aliases are: BITBUCKET, BITBUCKET_CLOUD, BITBUCKET_SERVER, STASH, BCVS, GIT, GITHUB, MERCURIAL, PERFORCE, SUBVERSIONThere are built-in notifications and others provided by add-ons. A recipient type may have additional parameters. Generally, these can be specified by the field and values parameters. In some cases, pre-defined parameters are available.
	 Required parameters: repositoryplan, orevent, namerecipientType
	 Optional parameters: planrecipient, repositoryKey, replace, fields, field1, value1, field2, value2, field3, value3, field4, value4, field5, value5, field6, value6, field7, value7, field8, value8
updateRepository - Update a global or plan repository.
	 Required parameters: repository or id, value7, field8, value8
removeNotification - Remove a plan notification. Use id of -1 to remove all notifications for a plan.
	 Required parameters: plan, id
addVariables - Add global or plan variables. Defaults to global variables unless a plan is specified. Use the field parameters for the variable name and the corresponding value parameters for the variable values,
	 Optional parameters: plan, replace fields, field1, value1, field2, value2, field3, value3, field4, value4, field5, value5, field6, value6, field7, value7, field8, value8
removeRepositoryupdateVariables - Remove global or plan repository. Use @all to remove all repositories.
	 Required parameters: repository or id
	 Optional parameters: plan, continue
getRepository - Get details of a global or plan repository. Sets the repository and repositoryId replacementUpdate existing global or plan variables. 	Defaults Requiredto parameters:global repositoryvariables 	 Optional parameters:unless a plan orderRepositoryis -specified. OrderUse repository in the listfield ofparameters repositoriesfor forthe avariable plan.name Defaultsand tothe movecorresponding thevalue repositoryparameters tofor the top to make it the default repository. Otherwise specify the after respository name.
	 Required parameters: plan, repository
	 Optional parameters: after
addRequirement - Add requirement to a plan job.
	 Required parameters: plan, job, requirementvariable values,
	 Optional parameters: plan, fields, field1, value1, field2, value2, field3, value3, field4, value4, field5, value5, field6, value6, field7, value7, field8, value8
removeVariables - Remove global or plan variables. Specify the variable names using the field parameters.
	 Optional parameters: typeplan, valuefields, updateRequirementfield1, -value1, Updatefield2, avalue2, plan requirement.
	 Required parameters: plan, job, id
	 Optional parameters: type, value
removeRequirement - Remove a plan requirement.
	 Required parameters: plan, job, id
addNotification - Add a plan notification. There are 2 parts to a notification - an event that triggers the notification and a recipient type that determines the notification protocol. There are built-in notifications and others provided by add-ons. A recipient type may have additional parameters. Generally, these can be specified by the field and values parameters. In some cases, pre-defined parameters are availablefield3, value3, field4, value4, field5, value5, field6, value6, field7, value7, field8, value8
addTrigger - Add a trigger to a plan. Pre-defined types are: polling, remote, scheduled. One or more repositories can be specified for pre-defined type triggers based on repositories. Polling triggers default to all plan repositories or use repository @all. Custom types can be specified with the appropriate trigger key (or alias) and all required parameters using the various field parameters. Use of the name parameter is deprecated - description should be used instead.
	 Required parameters: plan, event, recipientTypetype
	 Optional parameters: description, repository, schedule, ipRestriction, fields, field1, value1, field2, value2, field3, value3, field4, value4, field5, value5, field6, value6, field7, value7, field8, value8
removeNotificationremoveTrigger - Remove a trigger from a plan notification. Use id of= -1 to remove all notifications for a plan triggers.
	 Required parameters: plan, id
addAgent - Add a local agent.
	 Required parameters: plan, id
addVariables - Add global or plan variables. Defaults to global variables unless a plan is specified. Use the field parameters for the variable name and the corresponding value parameters for the variable values,
	 Optional parameters: plan, replace fields, field1, value1, field2, value2, field3, value3, field4, value4, field5, value5, field6, value6, field7, value7, field8, value8
updateVariables - Update existing global or plan variables. Defaults to global variables unless a plan is specified. Use the field parameters for the variable name and the corresponding value parameters for the variable values,
 agent
	 Optional parameters: description
removeAgent - Remove an agent.
	 Required parameters: agent
enableAgent - Enable an agent.
	 Required parameters: agent
disableAgent - Disable an agent.
	 Required parameters: agent
addAgentAssignment - Assign a project, plan, or job to a specific agent. This makes the agent is dedicated to only perform builds for all assignments. Use continue to ignore already exists error.
	 Required parameters: agent, assignment
	 Optional parameters: continue
removeAgentAssignment - Remove an assignment from a specific agent. Use continue to ignore not found error.
	 Required parameters: agent, assignment
	 Optional parameters: plan, fields, field1, value1, field2, value2, field3, value3, field4, value4, field5, value5, field6, value6, field7, value7, field8, value8
removeVariables - Remove global or plan variables. Specify the variable names using the field parameters.
	 Optional parameters: plan, fields, field1, value1, field2, value2, field3, value3, field4, value4, field5, value5, field6, value6, field7, value7, field8, value8
addTrigger - Add a trigger to a plan. Pre-defined types are: polling, remote, scheduled. One or more repositories can be specified for pre-defined type triggers based on repositories. Custom types can be specified with the appropriate trigger key (or alias) and all required parameters using the various field parameters. Alias types are: stashTriggercontinue
createDeploymentProject - Experimental. Create a deployment project for a plan.
	 Required parameters: plan, name
	 Optional parameters: description, branch
getDeploymentProject - Experimental. Get information for a deployment project by name or id.
	 Required parameters: deploymentProject
deleteDeploymentProject - Experimental. Delete a deployment project by name or id.
	 Required parameters: deploymentProject
	 Optional parameters: continue
addEnvironment - Experimental. Add an environment to deployment project.
	 Required parameters: deploymentProject, name
	 Optional parameters: description
getEnvironment - Experimental. Get information for an environment from a deployment project by name or id.
	 Required parameters: deploymentProject, environment
	 Optional parameters: file, encoding
removeEnvironment - Experimental. Remove an environment from a deployment project by name or id.
	 Required parameters: plandeploymentProject, name,environment
type
	 Optional parameters: repository, schedule, ipRestriction, fields, field1, value1, field2, value2, field3, value3, field4, value4, field5, value5, field6, value6, field7, value7, field8, value8
removeTrigger - Remove a trigger from a plan. Use id = -1 to remove all triggers. Server instances only.
 continue
deployEnvironment - Experimental. Deploy environment. To promote (re-deploy) an existing version, use --replace.
	 Required parameters: deploymentProject, environment, version
	 Optional parameters: build, number, replace
addEnvironmentTask - Experimental. Add a task to a deployment environment.
	 Required parameters: plandeploymentProject, idenvironment, addAgenttaskKey
-	 AddOptional aparameters: local agent.
	 Required parameters: agent
	 Optional parameters: description
removeAgent - Remove an agent.
	 Required parameters: agent
enableAgent - Enable an agent.
	 Required parameters: agent
disableAgent - Disable an agent.
	 Required parameters: agent
addAgentAssignment - Assign a project, plan, or job to a specific agent. This makes the agent is dedicated to only perform builds for all assignments. Use continue to ignore already exists errordescription, fields, field1, value1, field2, value2, field3, value3, field4, value4, field5, value5, field6, value6, field7, value7, field8, value8
addEnvironmentTrigger - Experimental. Add a trigger to a deployment project. Pre-defined types are: scheduled, afterSuccessfulStage. One or more repositories can be specified for pre-defined type triggers based on repositories. Custom types can be specified with the appropriate trigger key (or alias) and all required parameters using the various field parameters.
	 Required parameters: agentdeploymentProject, name, assignmenttype
	 Optional parameters: continuerepository, removeAgentAssignmentschedule, -ipRestriction, Removefields, anfield1, assignmentvalue1, fromfield2, avalue2, specific agent. Use continue to ignore not found error.
	 Required parameters: agent, assignment
	 Optional parameters: continuefield3, value3, field4, value4, field5, value5, field6, value6, field7, value7, field8, value8