VSTS - Build Definition - Multiple Agents

developer

In VSTS onlie, We have created a private pool and two agents are created (Say A, B). We want to create a build definition with two phases.

Is it possible to run first phase on Agent A and second phase on Agent B ?

Each phase, in agent selection it is showing <inherit from definition> instead of agents we have created to choose from.

Sheethal J S

Currently the capability of different agents per phase is not yet available in VSTS. We are working on the ability to set different agents on the phases.

Collected from the Internet

Please contact [email protected] to delete if infringement.

edited at
0

Comments

0 comments
Login to comment

Related

VSTS build agents - Can one computer run multiple build agents?

Build multiple projects/repositories with one build definition VSTS

VSTS Build Definition : adding multiple feeds in Nuget restore task

VSTS build number for build definition

If I run multiple VSTS build agents on the same machine, can they share a work folder?

VSTS On premise agents, build vs release?

Compile TeeChart applications on hosted build agents in VSTS

VSTS Build Agents VS Agents installed directly on the server (Deployment Groups). Which is more secure?

TeamCity multiple step build using different agents

Clone VSTS Build Definition in C#

How to specify folder for build definition in VSTS

JSON Transform Task in Build Definition in VSTS

Migrating a build definition from TFS to VSTS

Build definition for NETCore2 WebJob in VSTS

How to use $(Rev:r) in VSTS build definition?

VSTS build from multiple repositories

TFS 2013 Build: Running Unit Tests in Parallel on multiple build agents

How to build with --prod flag in VSTS build definition in azure

Understanding how multiple local TeamCity build agents work together

Does Jenkins offer a multiple build agents feature on VM like TeamCity?

How to output npm build error log files from linux hosted agents in vsts?

VSTS-hosted build agents refuse to run due to false capability error

Need the mail to be triggered upon success or failure of Build or release definition in VSTS

Continuous Integration on VSTS - Build Definition: No Files - System.AggregateException

VSTS - I want to use an existing deployment definition for a new build

Issue when updating build definition using the REST api of VSTS

VSTS build definition - prevent PowerShell exit behavior causing processes termination

VSTS YAML pipeline - pass project repository as parameter for the existed build definition

Using PowerShellGet on VSTS hosted agents