Deploying folder as artifact fails with 'Error storing the artifact...'

book

Article ID: 46533

calendar_today

Updated On:

Products

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

Issue/Introduction

Issue:

When we attempt to utilize a folder and its contents as an artifact utilizing 'Copy file or folder' core action, we will receive an exception in the agent and/or NAC logs similar to the following:

 

2016-04-28 14:04:17,776 [StageExecutorTask-121] DEBUG (com.nolio.releasecenter.services.internal.impl.ProblemsInternalServiceImpl:111) - Registering [1] problems for stage [1906].


2016-04-28 14:04:17,776 [StageExecutorTask-121] DEBUG (com.nolio.releasecenter.services.internal.impl.ProblemsInternalServiceImpl:99) - Registering stage [1906] problem: RCMessageData{msgCode=MessagesCodes{name=artifactDistributionDownloadFailed, code=99, messageType=DESIGN, level=ERROR}, args=[Artifact [ Def.Artef_SS3'ver. 2'], P4084LAB, Error storing the artifact - files\ART408\408\137\Builds (Accès refusé)]}

 

Environment:

This can occur within any combination of component types in our environment, whether it be database, release automation version, operating system, etc.

 

Cause:

Due to the multitude of filesystems, and how folders are handled for example on a remote network filesystem vs. a local filesystem of the same type even, this makes it very difficult to maintain continuity when it comes to having this action succeed.

 

Resolution:

This is officially not a supported method when it comes to defining an artifact.  Artifacts should always be files in order for the design to be supported.

Environment

Release: NOLNAC99000-6.1-Nolio-Automation Center
Component: