Question

Custom Repository Implementation - Trigger build after merging the branch

We are using custom repository for Deployment Manager.

We have configured a pipeline with merge policy enabled to “trigger deployment” on branch merge.

We are able to select the pipeline during branch merge process , but the branch doesn’t get merged and build was not triggered automatically.

It seems there are no extension points provided for custom repository in "Merge branch & trigger build process". Please let us know if this is known issue or does we have any extension points which are missed by us.

we are not able to find any extension points for adding logic to “pxPublishArtifact” activity whereas the same activity is present in respective OOTB supported repository classes and empty activity is available in parent repository class which is a Final Rule.

Correct Answer
August 8, 2019 - 2:04pm

We recently experienced this same issue when creating a custom Nexus component.

There is an additional activity that unfortunately needs to be implemented to support the devops merge wizard with custom repositories. We have a bug internally to address this in the platform, but in the meantime you can work around this.

The activity pxPublishArtifact must be implemented, which as you pointed out is a final rule so you will have to disable final rule validation in a private checkout to do this. Fortunately, it pretty much just needs to be a wrapper around the D_pxNewFile Data Page which you’ve already built.

We will be releasing nexus 2 connector for pega shortly which can serve as an example 

Reference: 

https://community.pega.com/knowledgebase/custom-repository-types

https://community.pega.com/knowledgebase/creating-and-using-custom-repository-types-deployment-manager

Comments

Keep up to date on this post and subscribe to comments

August 7, 2019 - 11:56am

Please follow the instructions here : https://community.pega.com/knowledgebase/creating-and-using-custom-repository-types-deployment-manager

If you follow those instructions, then Deployment Manager Merge branch  will work seamlessly with the new custom repository. 

 

 

 

August 7, 2019 - 1:29pm
Response to Linoy Alexander

Hi,

Builds triggered manually from deployment manager are working fine from end to end. Issue is only with the merge wizard where build should be triggered automatically.

Please note we are not able to find the rules mentioned in the below link (except - pyPingRepository)

https://community.pega.com/sites/default/files/help_v82/procomhelpmain.htm#repository/sm-custom-repository-connection-con.htm

August 8, 2019 - 2:04pm
Response to BharatG9850

We recently experienced this same issue when creating a custom Nexus component.

There is an additional activity that unfortunately needs to be implemented to support the devops merge wizard with custom repositories. We have a bug internally to address this in the platform, but in the meantime you can work around this.

The activity pxPublishArtifact must be implemented, which as you pointed out is a final rule so you will have to disable final rule validation in a private checkout to do this. Fortunately, it pretty much just needs to be a wrapper around the D_pxNewFile Data Page which you’ve already built.

We will be releasing nexus 2 connector for pega shortly which can serve as an example 

Reference: 

https://community.pega.com/knowledgebase/custom-repository-types

https://community.pega.com/knowledgebase/creating-and-using-custom-repository-types-deployment-manager