Broken Arrow : pivotal devops - Эдуард Кабринский

REMONTSit
Posty: 149
Rejestracja: 15 cze 2019, 2:01
Lokalizacja: USA
Kontakt:

Broken Arrow : pivotal devops - Эдуард Кабринский

Postautor: REMONTSit » 23 maja 2021, 4:31

Эдуард Кабринский - Azure artifact repository - Eduard Kabrinskiy


<h1>Azure artifact repository</h1>
<p>[youtube]</p>
Azure artifact repository <a href="http://remmont.com">Online news</a> Azure artifact repository
<h1>An Example Azure DevOps Release Pipeline for PowerShell modules</h1>
<h2>Introduction</h2>
<p>In the previous post I went over an example Azure DevOps Build Pipeline for PowerShell modules. This post will continue from where we left off and discuss the Azure DevOps Release Pipeline for PowerShell modules.</p>
<p>I?ll go over the different stages, and explain how the PowerShell modules are released to multiple internal Artifact feeds.</p>
<h2>Azure DevOps Release Pipeline</h2>
<p>First, let?s look at the example Azure DevOps Release Pipeline for my PowerShell module. My Azure DevOps project visibility is public for all to see, so you shouldn?t be prompted for a login.</p>
<p>The purpose of this Release Pipeline is to take Artifacts from the Build Pipeline, and release them to a stage. Here?s an example release showing deployments to all three stages (Dev, Test, and Prod).</p>
<p style="clear: both"><img src="https://adamrushuk.github.io/assets/ima ... elease.png" /></p>
<h3>Artifacts</h3>
<p>In the Release section above you can see the PowerShellPipeline Artifacts appear under the Continuous deployment heading. This shows a Release is triggered every time a Build Pipeline creates those Artifacts.</p>
<h3>Dev Stage</h3>
<p>We now move on to the stages. Note there is a line between Artifacts and the Dev stage, due to a Pre-deployment condition trigger set to After release:</p>
<p style="clear: both"><img src="https://adamrushuk.github.io/assets/ima ... rigger.png" /></p>
<p>This setting ensures the Dev stage is triggered automatically without user intervention.</p>
<h3>Test Stage</h3>
<p style="clear: both">The Test stage trigger is configured to start after the previous Dev stage, using an After stage trigger: <img style="float: left; margin: 0 10px 5px 0;" src="https://adamrushuk.github.io/assets/ima ... rigger.png" /></p>
<h3>Prod Stage</h3>
<p style="clear: both">Lastly, the Prod stage has a Manual only trigger: <img style="float: left; margin: 0 10px 5px 0;" src="https://adamrushuk.github.io/assets/ima ... rigger.png" /></p>
<p>This gives us the option to manually validate the Dev and Test environments are working as expected before we release to Prod.</p>
<h2>Stage Tasks</h2>
<p style="clear: both">All stages use roughly the same tasks, but let?s take a closer look into Prod: <img style="float: left; margin: 0 10px 5px 0;" src="https://adamrushuk.github.io/assets/ima ... -tasks.png" /></p>
<h3>Install NuGet</h3>
<p>The Install NuGet task is self-explanatory, and simply installs the specified NuGet binary version. NuGet is required to publish PowerShell modules to our internal Artifact feed.</p>
<h3>Additional Integration Tests for Prod Environment</h3>
<p>This task is a placeholder for actual test code, just to highlight you <em>could</em> run integration tests at this point if required. This might include provisioning infrastructure, loading data, then running tests and publishing the test results.</p>
<h3>Publish Module to Artifact Feed (prod)</h3>
<p>The final task is responsible for running a PowerShell script called Publish-AzDOArtifactFeed.ps1 , which takes two parameters: AzDOArtifactFeedName and AzDOPat :</p>
<p style="clear: both"><img src="https://adamrushuk.github.io/assets/ima ... e-task.png" /></p>
<p>The Arguments field shown above references Pipeline Variables $(artifact_feed_name) and $(artifact_feed_pat) , shown below:</p>
<p style="clear: both"><img src="https://adamrushuk.github.io/assets/ima ... iables.png" /></p>
<h2>Publish-AzDOArtifactFeed.ps1</h2>
<p>The code below has comments throughout, but the main steps are:</p>
<p><ol>
<li>Register a NuGet Package Source.</li>
<li>Register a PowerShell Repository.</li>
<li>Publish a PowerShell module.</li>
</ol>
</p>
<h2>Azure artifact repository</h2>

<h3>Azure artifact repository</h3>
<p>[youtube]</p>
Azure artifact repository <a href="http://remmont.com">News today</a> Azure artifact repository
<h4>Azure artifact repository</h4>
An example Azure DevOps Release Pipeline for PowerShell modules
<h5>Azure artifact repository</h5>
Azure artifact repository <a href="http://remmont.com">Azure artifact repository</a> Azure artifact repository
SOURCE: <h6>Azure artifact repository</h6> <a href="https://dev-ops.engineer/">Azure artifact repository</a> Azure artifact repository
#tags#[replace: -,-Azure artifact repository] Azure artifact repository#tags#

Eduard Kabrinskiy
current news

Kto jest online

Użytkownicy przeglądający to forum: Obecnie na forum nie ma żadnego zarejestrowanego użytkownika i 54 gości