Skip to end of banner
Go to start of banner

addTask

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 67 Next »

See also: Actions

Description

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_JIRA, CLI_SERVICE_DESK, CLI_SLACK, CLI_UPM, GANT, GINT, GRADLE, GRADLEW, GRADLEWRAPPER, GROOVY, INJECT_VARIABLES, JUNIT_PARSER, MAVEN2, MAVEN3, SCP, SQL, SCRIPT, SSH, VARIABLE_REPLACE. Use multiple field parameters to set required and optional fields specific for the task. Each task type may have unique fields that need to be determined from the respective UI panel. Missing or incorrect specifying of these fields will cause errors that are sometime hard to figure out. You can use a browser inspect capability to find the underlying field names and value requirements. Another, easier technique, is to create an example task in the UI and then use the exportJob action to see what ACLI has determined are the necessary fields. Use the @file special value to set the value of a field to the contents of the file (including standard input for -f "-") like '-a addTask --field scriptBody=@file --file script.txt'.

Required Parameters

plan, job, taskKey

Optional Parameters

description, disable, final, field, field1, value1, field2, value2, file, encoding

Type

Create

Category

Tasks

Output Formats

Replacement Variables

taskId

Since Version

Examples

addTask

Related How To's

  • No labels