Release Automation

Expand all | Collapse all

ROC - Get Artifact action unexpected behaviour in 5.5.

  • 1.  ROC - Get Artifact action unexpected behaviour in 5.5.

    Posted 06-18-2015 06:15 AM

    If a folder has been uploaded, the action download a zip without file extension. Getting the artifact in ROC gui it downloads as a .zip, as in 4.7.

    I would expect it to extract the archive as part of the action. Have the behaviour changed?

     

    I'm moving our existing flows from 4.7.1 to 5.5 and one change in the setup is using the "builtin" repository instead of external nexus.



  • 2.  Re: ROC - Get Artifact action unexpected behaviour in 5.5.

    Posted 09-11-2015 04:04 AM

    We ended up using the actions for zipping and extracting files to treat our old 4.7 Artifact Folders as 5.5 Artifact Archives, and are now looking into the 5.5 Artifact Package concept, building the packages from manifest instead of preparing them on disk in strictly named subfolders.

     

    A bigger headache was passing the destination directory of the package folder from the DeliverArtifacts process to the DeployComponent process. We used application parameters in 4.7, but for 5.5 we settled for for an external file created by one process to be queried by the next.

     

    All our existing 4.7 functionality are now validated in 5.5 and migrating the agents can begin. Thanks to all community contributors for sharing problems faced and solutions found here on the CA site. It may not give immediate answers to all issues we had, but it helped point to the viable workarounds.