Tasks Section

Top  Previous  Next

 

This section is only available to users that hold a Pro License

 

The tasks section allows User Sections to be assigned as Tasks and to become optional. When the script is executed, each task will be displayed with a check box to allow the user to determine whether or not those sections are executed.

lamp Note: Because this command can only be actioned via a User Interface it is ONLY available when using Pipeline Runner Studio  and is not available when you Run a Script from the Windows Command Line

Only one Tasks Section is allowed per script, and it must be located after the User Sections and before the Code section at the end of the script otherwise an error will be thrown. However, the number of tasks you can create is limited only by system resources.

 

Command Syntax

 

If you wish to create a Tasks section, you simply type the word Tasks into the script surrounded by square brackets:

 

[Tasks]

lamp Important: The Code section must be located after the User Sections and before the Code section at the end of the script. If it is not, an error will be thrown

Example

 

This example creates a Tasks section and adds two tasks to it.

 

[Tasks]

 

AddTask:PublishInstaller,PublishInstaller,Publish Installer

AddTask:UploadInstaller,UploadInstaller,Upload Installer

 

At runtime this would allow you to decide whether to publish the installer, upload the installer, or both.

 

To set out the script lines to be processed, simply create a standard User section for each task in the main body of the script with the Name of the task in it, and then enter the script lines to produce the desired reaction, like this:

 

[PublishInstaller]

; Script lines to process go here

 

See Also: AddTask Task Selection Dialog Setup Section Notification Section User Sections Code Section