This documentation relates to an earlier version of Bamboo.
View

Unknown macro: {spacejump}

or visit the current documentation home.

If a build was triggered by a code change, the commit comment (or check-in comment) will be shown in the build result.

On this page:

Viewing the Code Check-in Comments for a Particular Build Result

To view the code check-in comments for a particular build result:

  1. Navigate to the desired build result, as described on Viewing a Build Result.
  2. The build's commit comment will be shown to the right of the screen, under the heading 'Code Changes'.

注意

  • A note about build triggering* — There are a number of methods by which Bamboo can 'trigger' (i.e. execute) a Plan's build,
    • Build Strategy:
      • Code updated — a Plan's build is triggered whenever one or more authors checks in code.
      • Scheduled build — a Plan's build is triggered at scheduled times or specified time intervals.
      • Manual build — a Plan's build is only ever triggered manually.
      • Initial clean build — a Plan's build is triggered immediately after a new Plan has been created.
    • Build Dependency:
      • Dependency — a build can be triggered whenever another Plan's build is successfully completed.

    The trigger method for a Plan's build is listed in the 'Reason' column on the Dashboard.

関連トピック

Working with Comments
Triggering a Plan Build when Code is Updated





Except where otherwise noted, content in this space is licensed under a Creative Commons Attribution 2.5 Australia License.