BuildMaster 201: Pipelines
BuildMaster 201: Pipelines
-
Audience: Developers, Release Engineers, Ops, QA, Managers
-
Prerequisite: "BuildMaster 101: Fundamentals"
-
Students will go more in-depth into how a BuildMaster pipeline works. Topics include stages, approvals, deployment windows, variables, and more. At the end of this module, you should be comfortable designing a pipeline end-to-end.
-
Certifications Awarded Upon Completion: BuildMaster 201
Certification Workshops are included with the purchase of your InedoCon 2019 conference ticket. InedoCon attendees will receive the same quality certification experience that Inedo offers clients in our on-site training.
Outline/Structure of the Workshop
Certification Workshop.
Learning Outcome
See above.
Target Audience
Developers, Release Engineers, Ops, QA, Managers
Prerequisites for Attendees
BuildMaster 101: Fundamentals
schedule Submitted 1 year ago
People who liked this proposal, also liked:
-
keyboard_arrow_downMark Johnson - BuildMaster 101: Fundamentals
180 Mins
Workshop
Beginner
BuildMaster 101: Fundamentals
-
Audience: Developers, Release Engineers, Ops, QA, Managers
-
Students will learn about the pains of software deployments without automated tools. BuildMaster comes to the rescue by giving development teams an efficient system for implementing automated builds. In this lesson, you will walk through the fundamentals of using BuildMaster.
-
Certifications Awarded Upon Completion: BuildMaster 101
Certification Workshops are included with the purchase of your InedoCon 2019 conference ticket. InedoCon attendees will receive the same quality certification experience that Inedo offers clients in our on-site training.
-
-
keyboard_arrow_down
Mark Johnson - Provision and Manage Servers w/Otter, DSC, Git, and Chocolatey
45 Mins
Presentation
Intermediate
In this session, we will take a journey through the lifetime of a Chocolatey package across Windows servers in the enterprise. Some of the questions we will answer:
- How can we publish a Chocolatey package and have it automatically deployed across different environments using Otter and PowerShell DSC?
- How can we use Git to promote Chocolatey package configuration changes to different environments?
- How can Otter detect Chocolatey package version drift and automatically remediate it?
- How can we use Otter to take inventory of all installed Chocolatey packages? -