Hello,
Do you support any type of technical account that can be used for git repositories in Cloud Manager to push and pull code from external repositories(hosted. e.g. in Azure DevOps)?
解決済! 解決策の投稿を見る。
トピックはコミュニティのコンテンツの分類に役立ち、関連コンテンツを発見する可能性を広げます。
表示
返信
いいね!の合計
Hi @WojciechKa
Yes, you can push the code to the cloud manager repository using technical account, we use the same. example
https://github.com/jenkinsci/adobe-cloud-manager-plugin/tree/master/doc/config/adobeio-project
Hi @WojciechKa ,
Check this documentation: https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/implementing/usi....
In azure devops you can create pipeline to push azure repository branches to adobe git repository remote branch.
Hi @WojciechKa
Yes, It is possible to create technical account, please check
@WojciechKa Did you find the suggestion helpful? Please let us know if you require more information. Otherwise, please mark the answer as correct for posterity. If you've discovered a solution yourself, we would appreciate it if you could share it with the community. Thank you!
表示
返信
いいね!の合計
Hello @arunpatidar @konstantyn_diachenko @@Thank you for providing the documentation. After reviewing it, I still missing the answer to the question whether using the technical account you provided @arunpatidar @I can push the code to the cloud manager repository?
Hi @WojciechKa
Yes, you can push the code to the cloud manager repository using technical account, we use the same. example
https://github.com/jenkinsci/adobe-cloud-manager-plugin/tree/master/doc/config/adobeio-project
Hi @WojciechKa ,
I don't think there is a specific "service/technical account" for connecting to Adobe's Git repository. The available service accounts are typically intended for connecting to AEM servers, which is likely what the documentation provided by others refers to.
A common workaround is to create a dummy account and use it as a "technical account." You can see that the need for a real service account for managing Adobe's Git repository has already been requested here: Adobe Experience League Communities. Unfortunately, If this workaround does not work for you, consider following up directly with Adobe Support.
Hope this helps.