Creating build definitions

You can create IBM® Engineering Workflow Management build definitions that are based on various build templates, such as Ant, command line, or Maven. This topic describes how to create and configure a IBM Engineering Workflow Management client for Microsoft Visual Studio IDE build definition to run the MSbuild build command for MSTest unit tests. You can also configure a build definition to run the devenv.exe build command and use NUnit tests (only NUnit 2.x is supported).

Procedure

  1. In the Eclipse client, in the Team Artifacts view, expand the project folder.
  2. Right-click Builds; then click New Build Definition.
  3. In the New Build Definition wizard, on the New Build Definition page, accept the defaults and click Next.
  4. On the General Information page, in the Available build templates pane, select Jazz Build for Microsoft Visual Studio Solution – Jazz Build Engine and click Next.
  5. Optional: If you use Jazz source control, on the Pre-build page, select Jazz Source Control and click Next.
  6. On the Post-Build page, select MSTest Configuration and click Next.
  7. On the Additional Configuration page, select the appropriate options and click Finish.
  8. In the Build Definition editor, click the Microsoft Build tab and complete the following steps:
    Note: The MSBuild definition supports building multiple solutions and projects. To configure multiple solutions or projects, you can complete the fields below in table format.
    1. Click the MSbuild radio button.
    2. In the Path to build command field, type the location of the build command. For example, c:\WINDOWS\Microsoft.NET\Framework\v3.5.
    3. In the Solution file name field, type the name (including file extension) of the solution file to build. For example, Bank.sln.
    4. In the Build Configuration field, type the configuration to build. For example, Debug.
    5. Complete any remaining options.
  9. Click the MSTest Configuration tab and complete the following steps:
    1. In the Path field, type the path to MSTest.exe. For example, C:\Program Files\Microsoft Visual Studio 9.0\Common7\IDE\MSTest.exe.
    2. In the MSTest specification file field, type the name of the MSTest specification file to use. For example, AutoTests.trx.
    3. In the Additional arguments field, type any additional arguments to the MSTest command.
    4. In the Working directory field, type the directory to be used by the MSTest process.
  10. Optional: To schedule builds, complete the following steps:
    1. Click the Schedule tab.
    2. To enable build scheduling, under Schedule, select Enable.
    3. Click Add.
    4. In the Build Time pane, specify either continuous build intervals in minutes, or a specific build time.
    5. In the Build Days pane, select the days of the week that the build runs.
  11. Optional: If you selected Jazz Source Control in Step 5, complete the following steps:
    Note: It is highly recommended for the build definition to refer to a dedicated build workspace, rather than the team's stream, so that builds are isolated from ongoing changes in the stream.
    1. Click the Jazz Source Control tab.
    2. To specify a repository workspace, in the Build workspace pane, click Create.
    3. In the New Repository Workspace Wizard, on the Select a stream page, select Flow with a stream and in the lower pane, select the repository stream that you want to build from. This selection enables the repository workspace to accept changes from the stream.
    4. Click Next.
    5. On the New Repository Workspace page, in the Repository Workspace Name field, rename the repository workspace and click Next.
    6. On the Components to Add page, ensure that your component is selected.
    7. Ensure that the Load repository workspace after creation check box is cleared and click Finish.
    8. To specify a build user for the build workspace, in the Workspace Owner dialog box, to open the workspace, click Open Workspace.
    9. In the Repository Workspace editor, in the Owned by field, browse to the location of your special-purpose build user.
    10. Click Save.
    11. In the Build Definition editor, in the Load Options pane, in the Load directory field, type the path to the directory on the build machine where workspace files load.
    12. Optional: To define a subset of component files and folders for the build to load, select Load components by using a load rule file and select a load rule file. When a load rule file is specified, only those components that have load rules specified are loaded, and they are loaded according to those rules.
  12. Click Save.

What to do next

In the IBM Engineering Workflow Management client for Microsoft Visual Studio IDE, in the Team Artifacts window, you can navigate to the Builds folder (under the project folder) and request builds or view build results. You can also use a context menu action to move a build definition folder (or build definition). For information about creating build definition folders, see Organizing build definitions into folders.


video icon Video

Jazz.net channel
Software Education channel

learn icon Courses

IoT Academy
Skills Gateway

ask icon Community

Jazz.net
Jazz.net forums
Jazz.net library

support icon Support

IBM Support Community
Deployment wiki