This documentation relates to an earlier version of Bamboo.
View

Unknown macro: {spacejump}

or visit the current documentation home.

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

A plan's artifacts are any reports, websites or files (e.g. JAR files) which you wish to keep after each build. Artifacts are copied to a subdirectory (/PLAN_KEY/download_data/) under your 'Build Directory' folder (see Locating Important Directories and Files). Artifacts which you define in the plan are listed in each build result as User-defined artifacts (see Viewing a Build's Artifacts in the Bamboo User's Guide).

To specify a plan's build artifacts,

(info) If you are creating a new plan, start at step 5.

  1. Click 'Home' to go to the Dashboard.
  2. Click the 'All Plans' tab.
  3. Locate the plan in the list and click this icon:
  4. The 'Configuration' tab will be displayed. Click the 'Build Artifacts' sub-tab.
  5. The 'Build Artifacts' tab will be displayed (see screenshot below).
    • In the 'Artifact Label' field, specify the name which Bamboo will use to describe the artifact.
    • In the 'Source Directory' field, specify the directory (including path) where Bamboo will look for your artifact.
      (info) The source directory is relative to the build directory, do not use absolute path to refer to the 'source directory'
    • In the 'Artifact Copy Pattern' field, specify the name (or Ant file copy pattern) of the artifact(s) you want to keep.
      (info) The artifact copy pattern is relative to the source directory specified.
  6. Click the 'Save' button if you are editing an existing plan; or if you are creating a new plan, click the 'Next' button and go to Specifying a Plan's Notifications.

For example, if you want to keep the latest version of a JAR you have built, you could specify Artifact Copy Pattern to be '*/.jar' and the Source Directory to be 'target'.
Screenshot: 'Build Artifacts'_

  • No labels



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.