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
Right now these templates will exclusively publish to an internal repository and are only used by internal "private" code. This should be adapted for our open source modules (contained in this org) to run the build, tests, and publish to psgallery in a public azure devops org so that external contributors can see what's happening, but should also trigger another internal pipeline in our private org that will deploy the module to internal machines.
Make a new root template similar to umn-module, probably creatively named public-module, can probably use the same build and test templates.
A new "deploy" step that would deploy to psgallery and create a github release when appropriate
public-module would run in a public azure devops org
A new deploy-only pipeline/template created in the the private org that would be triggered by the public pipeline under certain conditions that would consume the publicly created build artifact, publish it to local repo (at least for testing) and install on local clients using existing private environment agents
For a "production" release I'm not sure if I'd publish the module internally and install from there or just install it directly from the psgallery
The text was updated successfully, but these errors were encountered:
Right now these templates will exclusively publish to an internal repository and are only used by internal "private" code. This should be adapted for our open source modules (contained in this org) to run the build, tests, and publish to psgallery in a public azure devops org so that external contributors can see what's happening, but should also trigger another internal pipeline in our private org that will deploy the module to internal machines.
The text was updated successfully, but these errors were encountered: