UcmPsTools Documentation
  • Welcome! - UcmPsTools
  • Using UcmPsTools
    • QuickStart
    • About UcmPSTools
    • Using UcmPsTools in your Automation
    • Cmdlet Reference
      • Accounts and Voice Apps
        • New-UcmOffice365User -todo
        • New-UcmTeamsResourceAccount - todo
      • Auditing and Planning
        • Measure-UcmOnPremNumberRange
      • Call Management
        • New-UcmCsFixedNumberDiversion
      • Connections and Modules
      • Licences and Service Plans
      • Reporting and Logging
        • Complete-UcmReport
        • Export-UcmCSVReport
        • Export-UcmHTMLReport
        • Initialize-UcmReport
        • New-UcmReportItem
        • New-UcmReportStep
        • Search-UcmCsOnPremNumberRange
        • Write-UcmLog
    • Example Scripts
  • UcmPsTools In Depth
    • More about UcmPsTools
    • Security In UcmPsTools
    • UcmPsTools Cmdlet Status Reporting
  • Contributing to UcmPsTools
    • New Function Rules
    • Pull Process
Powered by GitBook
On this page
  1. Contributing to UcmPsTools

Pull Process

Previously, I was using an Azure Pipelines workflow for CI/CD of the UcmPsTools module, but with issues due to CryptoMiners and the availability of GitHub Actions. All CI/CD has been moved to GitHub Actions.

Upon a successful pull into either Dev or Main, the following actions will occur.

  • The Pester tests in ./UcmPSTools.Tests.ps1 will be executed including importing all the functions in the ./public folder

  • All files in the ./public folder will be tested with PSScriptAnalyzer

  • Each of the PS1 files in ./Public will be signed with a digital certificate

  • A new version of the Module will be compiled for the Releases page

  • The module will be uploaded to the PowerShell Gallery (Main Branch Only)

PreviousNew Function Rules

Last updated 2 years ago