Build tasks will run sequentially in the order specified in the job.Tasks can be designated as build tasks or final tasks in a job: See the following pages for further details: Complete the remaining fields, which are specific for individual task types.Make task run only when a certain condition is met. Complete the following fields that are common to all task types:Įnter a description of the task, for display in Bamboo.Ĭheck, or clear, to selectively run this task.creating a new plan (you will be configuring tasks for the default job).selecting the Tasks tab when configuring an existing job, or.Navigate to the tasks configuration for a job.When creating a new plan, you can configure the tasks for the plan's default job. If you specify an Ant, Grails or Maven executable, you will also need to choose a JDK. You must specify an executable for each task. When creating a new job or configuring an existing one, you need to specify the tasks that will execute the job's builds.
For example, before executing a Maven goal, the user could substitute specific files within the working directory, substitute version numbers, check out source repositories, or execute a script.įinal tasks for a job are always executed, even if previous tasks in the job failed. A job can be configured to execute a number of tasks, on the same working directory. Tasks are configured within the scope of a job. Tasks may make use of an executable if required. Is run sequentially within a job on a Bamboo working directory.Is a small discrete unit of work, such as source code checkout, executing a Maven goal, running a script, or parsing test results.
0 kommentar(er)
