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 code changes will be shown in the build result.
 

To view the code changes that triggered a particular build result,

  1. Go to the build result.
  2. Click the 'Changes' tab.
  3. A list of updated files will be shown. Click the filename to view the changes; or, click the version number to view the entire file; or, click the 'diffs' links to view the differences between the current and previous version of each file.


Screenshot: 'Code Changes'

Showing code changes

  • Links to individual source-code files will only be available if your Bamboo administrator has specified a 'Web Repository URL' in the build's plan. For details please see Specifying a Plan's Source Repository in the Bamboo Administrator's Guide.
  • If there are no code changes since last build (in case of a manual build) there will not be any changes displayed on screen. 


A note about build triggering


There are a number of ways in which a build can be triggered for a plan,
  • Build Strategy:
    • Code updated — a build can be triggered whenever one or more authors checks-in code.
    • Scheduled build — a build can be scheduled to occur at regular intervals.
    • Manual build — a build can be triggered manually.
    • Initial clean build — a build will be triggered when a new plan is created.
  • Build Dependency:
    • Dependency — a build can be triggered whenever a successful build occurs for another plan.

The way in which each build was triggered is listed in the 'Reason' column on the Dashboard.




Log a request with our support team.



Raise an issue for our developers.



See answers from the community.



Tweet, blog and update our documentation.

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