Question

3
Replies
239
Views
Li Li (LiL95470)
W&W

W&W
US
LiL95470 Member since 2015 15 posts
W&W
Posted: February 22, 2018
Last activity: March 27, 2018
Posted: 22 Feb 2018 5:17 EST
Last activity: 27 Mar 2018 10:23 EDT
Closed

Deployment Manager-publish application archives into a repository

From https://pdn.pega.com/devops-release-pipeline-overview/devops-release-pipeline-overview i have learned, we could publish the exported application archives into a repository such as JFrog Artifactory to maintain a version history of deployable applications.

Are there any other preconditions for doing that besides a predefined RAP-rule?

In other words, is this step an automated step? Does it means, when the application was exported, the archive file was saved into repository automatically?

As far as i know, once the Applicaiton was exported, it would be save on a default ServiceExportPath(a tempDir).

I have created a Repository of JFrog Type, have tested with the DeploymentManager Release Pipeline, it has throwed an error msg at the first step.

ps: Can somebody give an example, how to fill the fields HostID and Repository key? According to the help document: Repository key is the root location on the JFrog server under which all artifacts are stored. But i don't know, what is the root location.

HostID:http://localhost:8081

Repository key: /artifactory/webapp/#/artifacts/browse/tree/General/generic-local

DevOps
Moderation Team has archived post, This thread is closed to future replies. Content and links will no longer be updated. If you have the same/similar Question, please write a new Question.