Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[ALM Accelerator - templates repo usage in multiple projects instead of adding to each project ] #5973

Closed
lingutla123 opened this issue Jun 29, 2023 · 5 comments
Assignees
Labels
alm-accelerator ALM Accelerator Components and Apps question Further information is requested

Comments

@lingutla123
Copy link

What is your question?

Hi Mike,

Do we need ALM Accelerator template repo in each project? We have many CRM application code projects in DevOps, thinking that if we can have ALM accelerator template repo at root level/separate project and reuse it in all projects instead of adding ALM Accelerator template repo in each project. Is this something possible?

Thank you!

What component are you experiencing the issue with?

ALM Accelerator Pipelines

What solution version are you using?

April 19th 2023

@lingutla123 lingutla123 added alm-accelerator ALM Accelerator Components and Apps question Further information is requested labels Jun 29, 2023
@mikefactorial
Copy link
Collaborator

@lingutla123 yes this is possible and a lot of other organizations setup their projects this way. If you're using the Project Setup Wizard to setup the projects for storing your solutions you can point to an existing project for where the pipeline templates live. This will generate the export, import and delete pipelines in the project where the solutions are stored but point to the templates that live in another project. Similarly, when the deployment pipelines are generated for the solution they will point to the central repository for the templates. You will need to ensure that the pipelines are able to access the templates in another project by turning off the following setting in the Organization Settings of your Azure DevOps org.

image

@mikefactorial mikefactorial self-assigned this Jun 30, 2023
@lingutla123
Copy link
Author

Thank You.

@mikefactorial
Copy link
Collaborator

Closing this out for now. Feel free to reopen if you have issues.

@CoEStarterKitBot
Copy link
Collaborator

@lingutla123 This has been fixed in the latest release. Please install the latest version of the toolkit following the instructions for installing updates. Note that if you do not remove the unmanaged layers as described there you will not receive updates from us.

@lingutla123
Copy link
Author

Closing this out for now. Feel free to reopen if you have issues.

Hi Mike,

I have existing PowerApps project in DevOPs and trying to set up Pipelines using the "COE templates project" without creating separate repo for Templates in Power Apps project. For this, when I use Project Setup Wizard and select existing Power App Project, getting below error. Does reuse /refer to COE templates without creating template repo in PowerApps supported for empty/new projects only?

Thanks much!
image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
alm-accelerator ALM Accelerator Components and Apps question Further information is requested
Projects
Status: Done
Development

No branches or pull requests

3 participants