Secondary processes are processes that are run after a successful build, and build
artifacts are generated and stored.
Before you create a secondary process template, create the project template to which you
want to attach it. Create the workflow that you want to assign to the template. See, Creating process definitions. If you want to configure resources for the template,
create them before you start to work on the template. See, Creating lockable resources.
Secondary processes inherit most of their configuration properties from the build workflow. After
a secondary process is complete, the data is presented on the dashboard, under the same build life
number as the parent build. Typically, secondary processes are used for testing.
-
From the IBM® UrbanCode™
Build dashboard,
click Templates, then click Process.
-
Click Create.
-
Using the New Process Template dialog, type a name for the source template
in the Name field.
-
Select Secondary Process from the Type
list.
-
Define a process for the
template.
-
Add a resource to the template.
Resources can be added during design time, or added dynamically by a script.
-
Using the page for the process template, click Add Resource.
-
Using the Add Resource to Lock dialog, determine whether you want to add
the resource now, at design time, or add the resource at run time with a script.
To add a resource at design time, select it from the Explicit Resource
list. Otherwise, enter a BeanShell script in the Scripted resource area. The
script must return the name of the resource, or a LockableResource object. To use a property, you
use this syntax return PropertyLookup.get("property_name")
. If the property returns
null or an empty string, no lock is used during the build. If the name resource does not exist, it
is created.
-
To obtain an exclusive lock on the resource, select Yes for the
Exclusive option.
-
Click Save.
-
Add properties to the template. See, Creating project template properties.
-
Click Done.