Q:

Azure DevOps Server 2019 (on-premises): Can agent jobs be run serially?

I have a scenario where I would like a build to start running on one agent (Job 1), and then after doing some work, I'd like it to run a step on a special agent (pool) of machines with specially licensed software.  (Job 2).   When that is done I'd like the rest of the build to complete on the original agent (Job 3).
I have been able to use "Variable Tools for Azure DevOps Services" to successfully pass any number of variables between agent jobs, even when they are running on different machines.   It is no problem for me to pass a UNC path from Job1 to Job2 / Job3, etc.
However, what I am seeing is that no matter what I do, agent jobs are always running in parallel, and there is no way to get them to run serially, unless they are locked to the same agent on the same machine, which defeats the whole purpose.
Does anyone know of a means to accomplish this?   Right now in tests, I have to use "Start-Sleep" or something similar, and repeatedly monitor an external event.   A terribly inelegant work-around.

A:

I found the answer.   A job properties contains a field called "dependencies".   You can make it serial by setting a dependency on the previous job.

