Checking packaging results

Open the Builds view to confirm that your package ran successfully.


  1. Select Window > Show View > Other > Team Build > Builds and click OK.
    The Builds tab opens.
  2. When packaging is finished, a green check mark indicates a successful package, or a red circle with an X indicates a failed package. Double-click a packaging request to open the Packaging Results view.
    The Packaging Results view opens.
  3. In the Packaging Results view, double-click the link to the log file associated with your packaging request to view more details about your package. You can also go to the Logs tab and double-click the log file that is associated with your packaging request. Review the Build Agent Service Log to debug any problems that are related to a failed package.
  4. If your package ran successfully, and if it was a work item package, select the Overview tab to see how many objects were packaged, the application name, the application version, and the work items included. In the Reported Work Items section, the work item summary page is attached. You can double-click it to see a summary of what was packaged.
  5. Select the Package Summary tab for more package information, including a table that lists all of the packaged objects. For IBM® i and z/OS® work item packages, you can double-click any entry in the Packaged Objects portion of the Contribution Summary field to view the work item that is associated with that object.
  6. If you selected Publish Manifest or Publish Package, you can see those files on the Downloads tab.
    The Downloads tab is available only if you select either Publish Manifest or Publish Package in your package definition.
  7. Verify that a new package is in the package directory on your build system:
    • IBM i or z/OS: (Package Root Directory)/(TimeStamp)
    • Linux: (Package Root Directory)/(Application Name)/(Application Version)/(TimeStamp)
    Note: For Linux, complete packages begin with the letter C, followed by a time stamp. Update (partial) packages begin with the letter U (for update package), followed by a time stamp. For example, a complete package that ran on the first day of June 2013, would be labeled in your package directory like this sample label: C20130601.

What to do next

You can deploy your packages by completing the steps in these tasks:
  1. Creating a deployment definition
  2. Requesting a deployment
You can set schedules, query your package and deployment results, and export your query results by completing the steps in these tasks:
  1. Scheduling packages and deployments
  2. Querying packages and deployments
  3. Exporting package and deployment query results