Skip to content
This repository contains all necessary files to create your own company CI/CD-like Powershell repository (step by step set up tutorial included). Please check EXAMPLES to get better idea of this solution features.
PowerShell Shell
Branch: master
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
.github
repo_content_set_up PS_env_set_up: to EN Oct 16, 2019
1. HOW TO - INITIAL CONFIGURATION.md Update 1. HOW TO - INITIAL CONFIGURATION.md Oct 16, 2019
2. HOW TO USE - EXAMPLES.md Update 2. HOW TO USE - EXAMPLES.md Oct 16, 2019
3. SIMPLIFIED EXPLANATION OF HOW IT WORKS.md Update 3. SIMPLIFIED EXPLANATION OF HOW IT WORKS.md Oct 17, 2019
README.md Update README.md Oct 17, 2019
WUG slajdy.pptx WUG slajdy: initial Aug 29, 2019
jak zprovoznit CICD Powershell repo.pptx slajd: new Oct 16, 2019

README.md

CI/CD solution for (not just) PowerShell content management in your Active Directory environment

Repository contains necessary files to create your own company CI/CD-like Powershell repository.

To set up please follow instructions

In case you found any bug or have improvement suggestion, please contact me at ztrhgf'at'seznam.cz.

Main features:

  • unified Powershell environment across whole Active Directory
    • same modules, functions and variables everywhere
    • one global Powershell profile to unify user experience
  • fully automated code validation, formatting and content distribution
    • using GIT hooks, Powershell scripts, GPO and VSC editor
    • automation is not applicable to code writing and making commits :)
  • possibility to distribute selected content to selected computers (to specified folder (with specified NTFS permissions))
  • can be used to distribute any kind of content (ps1, exe, ini, whatever) across company
  • easy to use (fully managed from Visual Studio Code editor)
  • no paid tools needed
  • GIT knowledge not needed
  • idiot-proof
    • warn about modification of functions and variables used in other scripts in repository etc
  • customizable (everything is written in Powershell)
  • automatic script signing (if enabled)
  • check examples for getting better insight

How code validation works

  • after you commit your changes, pre-commit git hook initiate checks defined in pre-commit.ps1
  • only if all checks are passed, commit will be created

How distribution of content works

  • after successful commit, content is automatically:
    • pushed to GIT repository
    • pulled to local server, processed and distributed to DFS share
    • from DFS share the content is downloaded to clients in your Active Directory

Changelog

[Unreleased]

  • support defining multiple object with same folderName key in $customConfig
  • support nesting of folders in Custom folder
  • support for Pester testing

[2.0.5] - 2019-10-16

Changed

  • important comments and error messages changed to english

[2.0.4] - 2019-10-4

Added

  • possibility to automatically sign Powershell code
    • just set up and uncomment definition of $signingCert variable in repo_sync.ps1

[2.0.3] - 2019-10-3

Added

  • possibility to sync modules just to chosen computers (defined in modulesConfig.ps1)

Changed

  • $config variable defined in customConfig.ps1 renamed to $customConfig to honor name of the script file and be more unique
  • repo_sync.ps1 now sync changes to DFS everytime, not just in case, some new data was pulled from cloud repo

Bug fixes

  • minor fixes

[2.0.2] - 2019-10-1

Added

  • check, that commited scripts are compatible with Powershell 3.0 (defined in PSScriptAnalyzerSettings.psd1, so edit it, if you wish to check PS Core compatibility etc)

[2.0.1] - 2019-9-27

Bug fixes

  • minor fixes

[2.0.0] - 2019-9-22

Breaking change

  • $config key customNTFS was renamed to customDestinationNTFS
  • $config key customShareNTFS was renamed to customSourceNTFS

Bug fixes

  • Repo_sync newly works with most actual data (loads Variables module and customConfig.ps1 right from local cloned repo, prior to loading from DFS share, which could lead to problems in some situations)

Added

  • Granting access to global Powershell profile (scripts2root\profile.ps1) stored in DFS to just computers listed in $computerWithProfilefolders. Non other machines can access it.
  • Possibility to copy Custom folder to any given local or shared path
  • Possibility to copy just content of Custom folder
  • Validation of $config variable stored in customConfig.ps1
  • Multiple accounts could be defined in customDestinationNTFS (customNTFS)
  • Warn about commited files, that contain #FIXME comment
  • TAB completition of computerName parametr in any command defined in Scripts module through using Register-ArgumentCompleter in profile.ps1

Changed

  • Update-Repo and Export-ScriptsToModule functions was moved to Repo_sync.ps1

[1.0.3] - 2019-9-2

Added

  • Possibility to define custom share NTFS rights for folders in Custom. Intended for limiting read access to folders stored in share/DFS, in case the folder doesn't have computerName attribute in customConfig, etc access isn't limited already.

[1.0.2] - 2019-8-30

Changed

  • Later import of the Variables module in PS_env_set_up.ps1 script. To work with current data when synchronyzing profile and Custom section.

[1.0.1] - 2019-8-30

Added

  • Granting access to folders in DFS repository "Custom" to just computers, which should download this content. Non other machines can access it.

[1.0.0] - 2019-8-29

Added

  • Initial commit
You can’t perform that action at this time.