Bamboo 1.0 : Appendix A. Bamboo Glossary
This page last changed on May 04, 2007 by admin.
activity logEvery plan has an activity log. An activity log is a temporary display of the latest output from the plan's most recent build log. artifactAn artifact (e.g. a JAR file) is something created by a build. A build's artifacts are specified in the build's plan by a Bamboo administrator. authorAn author is any person who checks-in code to a repository that is associated with a Bamboo plan. An author need not be a Bamboo user. buildA build is one execution of a plan. Every build has a Build Number, which is appended to the relevant Plan Key to form the Build Key. For example, if a plan with the key "CRM-BRANCH" is executed for the seventeenth time, the build key will be "CRM-BRANCH-17". build activityBuild activity is the number of builds that occur in a given period of time. build durationBuild duration is the total time taken to execute a build plan — that is, the time taken to compile the code and run all of the plan's tests.
build logEvery build has a build log. A build log is a permanent record of all the output generated by compiling the plan's source-code and executing the tests. build planSee plan. build queuebuild resultEvery completed build has a build result:
Additionally,
build telemetryBuild telemetry is the insight provided by Bamboo's dynamic reports, charts and collation of build metrics. Build telemetry helps identify trends across build plans and across authors — not just focusing on the results of a single build. builderA builder is a software compiler program external to Bamboo. Bamboo supports multiple builders. Once a builder is defined in the Bamboo system, it can then be specified in build plans by a Bamboo administrator. labelA label is a convenient way to tag and group build results that are logically related to each other. Labels can also be used to define RSS feeds. Labels can be applied to build results automatically, by specifying the label(s) in a build plan (note that only Bamboo administrators can do this). Labels can also be applied ad-hoc to build results by Bamboo users. plan
A plan defines: what gets built (i.e. the source-code repository); how the build is triggered; which builder to use; what tests to run; what artifacts the build will produce; who will be notified of the build result; and any labels with which the build result or build artifacts will be tagged. Every plan belongs to a project. projectA project is a collection of plans.
triggering
The way in which each build was triggered is listed in the 'Reason' column on the Dashboard.
Return to Bamboo 1.0 Documentation Home |
![]() |
Document generated by Confluence on May 09, 2007 00:13 |