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
DevOps with Windows Server 2016

You're reading from   DevOps with Windows Server 2016 Obtain enterprise agility and continuous delivery by implementing DevOps with Windows Server 2016

Arrow left icon
Product type Paperback
Published in Mar 2017
Publisher Packt
ISBN-13 9781786468550
Length 558 pages
Edition 1st Edition
Languages
Arrow right icon
Author (1):
Arrow left icon
Ritesh Modi Ritesh Modi
Author Profile Icon Ritesh Modi
Ritesh Modi
Arrow right icon
View More author details
Toc

Table of Contents (12) Chapters Close

Preface 1. Introducing DevOps FREE CHAPTER 2. DevOps Tools and Technologies 3. DevOps Automation Primer 4. Nano, Containers, and Docker Primer 5. Building a Sample Application 6. Source Code Control 7. Configuration Management 8. Configuration Management and Operational Validation 9. Continuous Integration 10. Continuous Delivery and Deployment 11. Monitoring and Measuring

Build pipeline execution


There are multiple places from where build definitions can be executed manually in VSTS. In this section, a couple of different ways are explained for executing a build definition.

Build definitions can be executed using the context menu available against each build definition, as show here:

Figure 23: Queuing a build definition

If the build definition is in the edit mode, it can be executed by clicking on the Queue new build button in the top-right corner of the screen, as shown here:

Figure 24: Another way to queue build definition

The build progress can be viewed in the console window. This is shown in the following screenshot. Here, the left pane shows the execution of all activities available in the build definition that are in the enabled state. The right pane shows the log messages from activities about their progress and status. Any message in red color denotes failure, while green color means success:

Figure 25: Build execution progress and logs

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