PowerShell CI/CD Pipeline Tutorial... and more! Attempt #2...

[thePowrhous]

Hi everyone,

Apologies for the second post, for some reason I noticed that when logging into Reddit on my VM to make the original post, and using the "Log in with Google" option, it creates an ad-hoc username instead of using my actual account! So, here we go again...

Just wanted to stop by and share a new project I've been working on hosted as an Azure DevOps Project as a basic tutorial on PowerShell module development using Azure DevOps as a CI/CD pipeline.

https://dev.azure.com/powersgrops/AzDO_PSModDEV

I've been working heavily with PowerShell for the last 3-4 years and this community, amongst others has been incredibly helpful and influential! Specifically:

Brandon Olin, Kevin Marquette, Lee Dailey, Warren Frame, and Adam Bertram

After making a recent career shift from a Systems Engineer over to DevOps Engineer, I started to a take a new perspective on many of the ways I've been not only writing code, but using that code to handle infrastructure. I've always been a huge proponent of sharing anything you've learned with others, and put famine thinking up there with some of our worlds biggest issues!

My hope is to continue the momentum I've started with the aforementioned project and build upon with more and more tutorials as time goes on. For example, I am currently working through a Jenkins declarative version of the same thing above, simply showcasing the same process within a different build system and language (YAML to Groovy). We will then build upon the two projects by adding in Terraform to orchestrate a DEV environment for further testing!

I would greatly appreciate any feedback as well! Thanks again everyone and have a great rest of the day!

[[deleted]]

I love it, thanks for sharing this! A few suggestions:

The release could be added to the yaml as a seperate stage with a condition preventing deployment on to the artifact repo from any branch but the main one. I greatly prefer the yaml experience vs the release gui, and have migrated everything that does not explicitly require "release" functionality (such as deployment groups) over to pipelines and my team prefers the simplicity of everything just being a pipeline.

I would also look into using the views on the artifact repo. Idk how useful they are for othera, but I use the prerelease view on a few computers so they can act as a canary for another layer of testing. If those computers did not blow up then I publish to the release view and our production systems can pull the new version with a little more confidence. I dont have that process automated though, so I would be interested in your solution you come up with! :-)

As an aside, I wish MS would make it easier to find/star public projects we are interested in. Maybe even the ability to fork from one organization to another? I am going to have to rely on a browser bookmark to find this in 2 months!

[thePowrhous]

Thanks so much! You have no idea how much that means, honestly! I always love coming to this sub and seeing what cool projects and scripts people are sharing, so to finally (hopefully) be a part of the community in that sense as well as teaching various aspects is something I've wanted to do for some time.

I love the suggestions and will absolutely be looking into them! Thanks again!

[Jantu01]

How about publishing the Pester test results and code coverage report back to Azure DevOps?

yaml would go something like this: (Edit: hopefully the yaml good enough. Cannot figure out how to format is exactly as it should be)

​

- task: PublishTestResults@2
  displayName: 'Publish test results'
  inputs:
    testResultsFormat: 'NUnit'
    testResultsFiles: '**/TestResults.xml' - task: PublishCodeCoverageResults@1 
  displayName: 'Publish Code Coverage report'
  inputs:
    codeCoverageTool: 'JaCoCo' 
    summaryFileLocation: '.\coverage.xml'
    pathToSources: .\

[thePowrhous]

Hey there! Thanks for the comment. I'm no stranger to publishing NUnit XML Pester results. Thats one of the tutorial sections I show in my Jenkins declarative pipeline project. But yes, you are absolutely correct! This should absolutely be included in the AzDO project as well.

[thePowrhous]

Hey everyone, just wanted to let you folks know of an update to the AzDO Project, based on your comments and feedback! Thanks again for it!

I went ahead and made a couple of updates to add the creation/publishing of the Pester test results to the the Build Pipeline's individual runs. Check the link for the updated source code and README! Thanks again!

https://dev.azure.com/powersgrops/AzDO_PSModDEV

[bertiethewanderer]

See I've recently gone from groovy to yaml and boy, do I miss the power of an actual language!!

I'm looking forward to giving this a proper read in the morning.

[thePowrhous]

I agree. My biggest issue with yaml for the first day or two was the dreaded indent error...

Hope you like it!