Slow Artifact Distribution

Products

• CA Release Automation - Release Operations Center (Nolio)
• CA Release Automation - DataManagement Server (Nolio)

Issue/Introduction

One of our deployments stayed in the Artifact Distribution stage for a long time (2 hours) before eventually failing. However, another deployment from the same template with a similar artifact (i.e. a rebuild of the same code after a minor code change and therefore not cached) which was started very shortly after completed in 10 minutes. Why did the first artifact distribution take so long?

Environment

Release : 6.6

Component : CA RELEASE AUTOMATION CORE

Cause

There are several areas that were found to be problematic. They include:

• The artifact retrieval agent used to retrieve the artifact.
• Network bandwidth, congestion, or other network related conditions that might cause file transfer delays. 

 

Resolution

For the causes described above, the areas to focus on would include:

• Configure the retrieval agent/group to utilize an agent that can access/download the file with speed. 
• Consult network team to identify possible bandwidth, congestion or other problems that might cause slow file transfers. 

Additional Information

The following information may assist your investigation:

• How To: Identify Artifact Retrieval Agent Used By Deployment
• How To: Identify How Long The Artifact Retrieval Process Took
• How To: Identify Bottleneck In NES_DISTRIBUTION Artifact Distribution Phase