CloudBees Accelerator provides features to organize builds in even the most complex environments. You do not need to create a build class—by default, a simple organizational structure is set up for you. But, if you have diverse product lines, or multiple product releases, you should set up and use build classes.
A build class is a flexible, user-defined classification for a designated group of builds. Using build classes is optional, but if you do not assign a build class, the Cluster Manager assigns the build to a default build class. Build classes help you organize the build management process.
Depending on your company requirements, you might use build classes to organize build groups by version or release, product type, development stage, or platform. You can decide how to use build classes to organize your builds into sets.
Classes have default priorities and boost values. Boost values have a range of -10 to +10 (default 0), where a higher value means that builds in that class can use available agents ahead of builds with the same priority but less boost.
Each build in a class is identified by a unique string called a tag . The build tag definition is a template that expands when a new build starts. The tag is user-defined and generally consists of a generic build name appended with build-specific data constructed from the following variables:
Globally unique number (Global Counter)
Number unique to the build class (Local Counter; the build serial number within the class)
User-defined build class name
System-generated number that the Cluster Manager uses to identify each class
Name of the user who invoked eMake
Name of the machine where eMake was invoked
Label specified at the eMake command line. For example,
Operating system ID under which the build was invoked. (
Build start date and time using variables
Year at build start time (
Year at build start time (
Sequential month number at build start time (
Sequential day of month at build start time (
Hour of the day at build start time (
Minutes at build start time (
Seconds at build start time (
Abbreviated day of week at build start time (
Full name of the day of week at build start time (such as
Abbreviated month name at build start time (such as
Full month name at build start time (such as
Build start date and time using the variables
Together, the build name and variables are referred to as the tag definition . Variable names are case-sensitive.
For example, the tag definition
%BUILD_CLASS%%LC%%DATE% for a build class named
QA_BUILD creates the following build tag:
When assigning build class tag definitions, choose from the list of tag variables above.
Suppose your company has two major product lines: SuperSoftware and MegaSoftware. SuperSoftware runs on Windows and Solaris platforms. MegaSoftware runs on Windows only. You could begin by setting up three classes that include the product name, the platform, and the current version number for each product:
You could name the first class SuperSoftware_Win_v.2.1. The tag definition for this class would be:
The result would be a series of builds each named, or tagged , with the product name, the platform, the version number, a serial number (unique to the class), and the date for each build. For example:
The second class could be named SuperSoftware_Sol_v.1.7. The tag definition can be the same as in our first example, because it would be distinguished by the second build class name. Build tags in the second class would look like:
The third class could be named MegaSoftware_Win_v.1.3. For this product, the tag definition would be similar to the previous examples but also could include the name of the user who started the build, because the MegaSoftware team is spread over several different locations. For this class, the tag definition might look like:
As in the first two examples, the result would be a sequentially-numbered series of builds with the product name, platform, version number, name of the user who ran the build, and date of each build assigned through the build class:
Additional classes could be created when the development of SuperSoftware or MegaSoftware entered a new phase, such as a new platform release or a new version release. In this way, the builds for each stage of development can be segmented into logical sets for a more manageable and organized workflow.
Open a web browser and go to the Cluster Manager host.
Click the Build > Build Classes tab.
The Build Classes page displays.
Click the New Build Class link.
A blank class details screen appears.
Click the Show Help link on the right side of the screen to see field descriptions ,and then fill in the fields accordingly.
In the Tag Definition text box, enter the build class tag definition.
To avoid errors, follow standard naming conventions for tag definitions by using numbers, letters, and underscores only without leading or trailing white spaces. Use underscores (
_ ) instead of spaces. Use a percent sign on either side of any variables used. (For example,
Continue filling in the fields.
See the online help for more information if needed.
|You can add comments to the build class. To do so, click the Build > Build Class tab, then select a build class name. For details about on adding or editing build class comments, adding or editing class properties, or deleting a build class, see the online help.|
Assign the build’s class name through the
--emake-class=<exact build class name> eMake command-line option when the build is invoked. If you do not assign a build class, the Cluster Manager assigns the build to the default class. If the class name typed on the eMake command line does not match a class name already in the Cluster Manager, eMake exits.
eMake automatically creates makefile macros (
ECLOUD_BUILD_TAG ) from Cluster Manager build class data. These macros can be used to place generated values in your makefiles. For details, see the “ Using eMake Variables ” section.