Closed Athystrup closed 2 months ago
This is no problem. The Template-option has nothing to do with ALOps licenses, but it's merely a DevOps feature, which will "gather" a pipeline from templates, and then start to execute it in your original project/repo.
Thank you for clarifying. This will really help us in not having to maintain the same yaml files across multiple repos!
Hi
We are currently running on the "RepositoryPer5" license and wish to create a new Azure project where we store our yaml templates, so that we can standarize execution of pipelines. However we are a little bit in doubt of whether that is allowed with the type of license we are using, as the template files would then be in another Azure DevOps project from the one where we are using the ALOps license.
Could you clarify whether this is allowed or alternatively what might be the best option to standarize templates?
Thank you!