Configuring a Linux or UNIX package definition

After you create a package definition, you can specify which binaries to package or where to store the package by modifying your package definition.

Procedure

  1. In the Team Artifacts view, expand the Enterprise Extensions node, then the Packages node.
    1. To create a package definition, right-click Packages, then select New Package Definition. The New Package Definition wizard opens. Select the appropriate options for your package, and click Finish. For more information about creating a packaging definition, see Creating a package definition.
    2. To modify an existing package definition, right-click the package definition you want to modify and select Open Package Definition. The Package Definition editor opens.
  2. On the Overview tab in the Package Definition editor, make sure that all of the default settings are correct. Change any that are not.
    1. Optional: In the General Information Description section, briefly describe your definition.
    2. Select Ignore warnings when computing overall status.
    3. In the Supporting Build Engines field, click Add to add a build engine, or Create to create one. Select the build engine you want, then click OK.
      Note: You must associate a build engine with your package definition. For more information, see Creating build engines.
    4. Optional: In the Pruning Policy section, select Prune build results, then set the number of successful and failed builds to save.
  3. Optional: Go to the Properties tab.
    1. In the Properties table, click Add, then select one of the following property types:
      • String
      • Repository Workspace
      • Resource Definition
      • Translator
      Click OK. The Add Build Property window opens.
    2. In the Add Build Property window, specify a Name, Value, and Description for your new build property. Click Edit to modify the Value field.
  4. Optional: Go to the Ant tab.
    1. In the Build File and Targets section, specify the Ant file and targets you want your definition to invoke. Reference properties using this format: ${propertyName}.
    2. In the Ant Configuration section, select Include the Jazz™ build toolkit tasks if you want to add the -lib Ant argument with the path to the Jazz buildtoolkit directory.
    3. Specify any other configuration details, including the following:
      • Ant home
      • Ant arguments. The default is -verbose.
      • Working directory
      • Java™ home
      • Java VM arguments. The default is -Xquickstart.
      • Properties file
  5. Go to the Linux/UNIX Packaging tab.
    1. In the Application section, name your application, briefly describe it (optional), and identify the application version you want to package.
    2. In the Package section, enter the path to your ship list file to specify which built members you want to package. You can also enter the path to an exclude file, if you created one. If your package is a complete application, select Complete package. If it is a subset of an application you want to apply as a fix pack, update, or program temporary fix (PTF), do not select Complete package. For more information about ship list filter files, see this topic: Creating a ship list filter file.
    3. In the Package root directory field, choose a directory on the build machine where you want to store all packages.
    4. In the Package pre-command field, specify a command to run on the build machine before packaging.
    5. In the Package post-command field, specify a command to run on the build machine after packaging.
    6. In the Platform section, specify a build root directory.
      Note: The path names you specify in the ship list filter file are relative to this build root directory.
    7. In the Publish section, select either Publish manifest or Publish package.
  6. Click Save.

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