Skip to content

Added missing ADO artifacts reference in wiki #851

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.

Sign up for GitHub

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

Merged
AlexanderSehr merged 1 commit into from
Jan 3, 2022
Merged

Added missing ADO artifacts reference in wiki #851

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions docs/wiki/PipelinesDesign.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -102,6 +102,7 @@ For additional details on how removal works please refer to the dedicated [Remov
The publish phase concludes each module's pipeline. If all previous tests succeeded (i.e. no phase failed) and the pipeline was executed in the [main\|master] branch, a new module version is published to all configured target locations. Currently we support
- _template specs_
- _private bicep registry_
- _universal artifacts_ (_Azure DevOps_ only)

By the time of this writing, the publishing experience works as follows:
1. A user can optionally specify a version in the module's pipeline file, or during runtime. If the user does not, a default version is used
Expand Down Expand Up @@ -392,3 +393,7 @@ While they look very similar they have specific areas in which they differ:
- name: modulePath
value: '/arm/Microsoft.AnalysisServices/servers'
```

#### Azure DevOps Artifacts

For _Azure DevOps_ we offer also the option to publish to _Azure DevOps_ universal packages. As the code is already available in the pipeline's publish template (`.azuredevops/pipelineTemplates/module.jobs.publish.yml`) you only have to specify the required information in the shared global variables file (`.azuredevops/pipelineVariables/global.variables.yml`) to enable the feature. For detailed information please refer to the variable file's `Publish: Universal packages settings` section.