Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Learn PowerShell Core 6.0

You're reading from   Learn PowerShell Core 6.0 Automate and control administrative tasks using DevOps principles

Arrow left icon
Product type Paperback
Published in Jul 2018
Publisher Packt
ISBN-13 9781788838986
Length 552 pages
Edition 1st Edition
Languages
Concepts
Arrow right icon
Authors (2):
Arrow left icon
David das Neves David das Neves
Author Profile Icon David das Neves
David das Neves
Jan-Hendrik Peters Jan-Hendrik Peters
Author Profile Icon Jan-Hendrik Peters
Jan-Hendrik Peters
Arrow right icon
View More author details
Toc

Table of Contents (21) Chapters Close

Preface 1. Current PowerShell Versions FREE CHAPTER 2. PowerShell ISE Versus VSCode 3. Basic Coding Techniques 4. Advanced Coding Techniques 5. Writing Reusable Code 6. Working with Data 7. Understanding PowerShell Security 8. Just Enough Administration 9. DevOps with PowerShell 10. Creating Your Own PowerShell Repository 11. VSCode and PowerShell Release Pipelines 12. PowerShell Desired State Configuration 13. Working with Windows 14. Working with Azure 15. Connecting to Microsoft Online Services 16. Working with SCCM and SQL Server 17. PowerShell Deep Dives 18. PowerShell ISE Hotkeys 19. Assessments 20. Other Books You May Enjoy

Continuous integration

Continuous integration describes the practice of multiple developers integrating code into the main repository multiple times. Every commit a developer adds starts a build that consists of several tests and produces artifacts when it is finished.

Countless open source repositories use continuous integration and have a build and release process to release to the PowerShell gallery for example. Especially in the open-source community, where projects have many different contributors, a good CI process is essential.

The PowerShell repositories set a good example. Developers fork the official code and work on their small features, which later need to be integrated into the repository. This is accomplished through pull requests:

Every pull request triggers an automated build process on a CI system like AppVeyor or VSTS that runs a suite of tests. So, before the...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime
Banner background image