You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Now that cmf-cli isn't responsible by scaffold pipelines, we should remove all the logic related to deployment directories and/or repositories.
This and this can be removed and also the repositories.json can be refactored to only contain the repositories array (it can be empty)
On cmf-cli this is only used by the assemble command and if we remove that logic from init, it will reduce the init complexity and doesn't break any backwards compatibility and keeps the flexibility.
To complement this, we should change our azuredevops pipelines scaffolding to call the assemble like this: cmf assemble --includeTestPackages --outputDir $(packageDir) --ciRepo $(artifacts)/CIPackages/$(Build.SourceBranchName) --repos $(artifacts)/Delivered
The text was updated successfully, but these errors were encountered:
Now that cmf-cli isn't responsible by scaffold pipelines, we should remove all the logic related to deployment directories and/or repositories.
This and this can be removed and also the repositories.json can be refactored to only contain the repositories array (it can be empty)
On cmf-cli this is only used by the
assemble
command and if we remove that logic from init, it will reduce the init complexity and doesn't break any backwards compatibility and keeps the flexibility.To complement this, we should change our azuredevops pipelines scaffolding to call the assemble like this:
cmf assemble --includeTestPackages --outputDir $(packageDir) --ciRepo $(artifacts)/CIPackages/$(Build.SourceBranchName) --repos $(artifacts)/Delivered
The text was updated successfully, but these errors were encountered: