This documentation relates to QuickBuild 5.0.x
Select here if you are using a different version

Store Build Artifacts on Agent

You are viewing an old version (v. 1) of this page.
The latest version is v. 3, last edited on Dec 18, 2012 (view differences | )
view page history | view next version >>

Since QuickBuild 5.0, build artifacts can be stored on one or more agents to reduce load of publishing and serving artifacts from QuickBuild server. For instance, one can edit advanced setting of a configuration to store artifacts of all its builds on desired agent as below:
!Unable to render embedded object: File (artifact storage setting on agent) not found.!
Thanks to the inheritance nature of configuration settings, all descendant configurations will also store artifacts on that agent unless they has its own artifact storage strategy defined.
When you decide to store artifacts on agent, please note that:

  1. You may need to tune your firewall setting to allow users accessing port of involved build agents to download build artifacts from GUI.
  2. You may need to tune the firewall setting to allow other agents accessing port of involved build agents to publish and download artifacts during a build.
  3. Users will be prompted to input their credentials again when downloading artifacts from GUI if artifacts are not allowed to be accessed anonymously on relevant build agents.
  4. By default artifacts are stored on agent under the directory <build agent install dir>/storage/<build id>/artifacts. So please be careful not to remove this folder when manually upgrade your build agent (manually upgrade build agent is generally not necessary as QuickBuild server can upgrade them automatically in most cases). If you'd like to store artifacts on some other places on agent, please tune the storage setting in advanced setting of relevant configuration. For instance, you may define storage setting in root configuration as below:
    !Unable to render embedded object: File (storage setting) not found.!
    Then all artifacts of all configurations in the system will be stored this way (assume you have not overwrite the storage setting in descendent configurations):
  5. If artifacts are stored on server, they will be stored to:
    <global storage directory defined in system setting>/builds/<build id>
  6. If artifacts are stored on agent, they will be stored to:
    • <directory denoted by user attribute artifactStorage>/builds/<build id> if user attribute artifactStorage is defined for the agent in grid page.
    • /mnt/storage if user attribute aritfactStorage is NOT defined for the agent.
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.