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 several methods by which Bamboo can 'trigger' (i.e. begin executing) a plan's build:

    Build Strategy

    • Code updated — ensures that a plan build only occurs when something changes in the plan's source repository (which may affect the outcome of a Plan build) .i.e. whenever one or more authors check in code.
    • Scheduled build — can allow a team to structure the day according to a predictable schedule. Scheduled builds are run regardless of whether or not any code changes have occurred i.e. at scheduled times or specified time intervals.
    • Manual build — allows you to ensure that builds are only triggered manually (or by the successful builds of other plans on which this plan is dependent).
    • Initial clean build — i.e. 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.

関連トピック

コメントでの作業