Book Image

Learn PowerShell Core 6.0

By : David das Neves, Jan-Hendrik Peters
Book Image

Learn PowerShell Core 6.0

By: David das Neves, Jan-Hendrik Peters

Overview of this book

Beginning with an overview of the different versions of PowerShell, Learn PowerShell Core 6.0 introduces you to VSCode and then dives into helping you understand the basic techniques in PowerShell scripting. You will cover advanced coding techniques, learn how to write reusable code as well as store and load data with PowerShell. This book will help you understand PowerShell security and Just Enough Administration, enabling you to create your own PowerShell repository. The last set of chapters will guide you in setting up, configuring, and working with Release Pipelines in VSCode and VSTS, and help you understand PowerShell DSC. In addition to this, you will learn how to use PowerShell with Windows, Azure, Microsoft Online Services, SCCM, and SQL Server. The final chapter will provide you with some use cases and pro tips. By the end of this book, you will be able to create professional reusable code using security insight and knowledge of working with PowerShell Core 6.0 and its most important capabilities.
Table of Contents (26 chapters)
Title Page
Dedication
Packt Upsell
Contributors
Preface
Index

CI tools


We already saw in Chapters 5, Writing Reusable Code and Chapter 10Creating Your Own PowerShell Repository which CI tools are available and what differentiates them. In our module build and release process, the CI tools should become irrelevant. In an enterprise environment, CI tools will give you more transparency and control over the build process, as well as proper test and release management.

Other than that, they are merely tools around your build script that orchestrate what to do with build artifacts. The build script does the heavy lifting and decides which actions to take based on the following:

  • Build environment (Dev, QA, Prod)
  • Build system (that is, TFS, VSTS, AppVeyor, Jenkins, and others)

Your build script contains the necessary build tasks, such as executing test cases and publishing artifacts. It should be designed in a way that you can simply lift and shift. Build locally, in TFS, or on AppVeyor—the build script remains the same.