VSTS：如何修改发布定义以使用本地代理解决发布无法运行问题
Got it, let's get this release pipeline sorted out right away. First, let's confirm the issue you're hitting: your Microsoft-hosted pipeline minutes are totally exhausted, which is why you're seeing that frustrating error:
Your account has no free minutes remaining. Add a hosted pipeline to run more builds or releases.
Since your builds are already working smoothly with your self-hosted (local) agent, switching your release pipeline to use the same agent is straightforward. Here's exactly how to do it:
Step 1: Open Your Release Pipeline
- Head to your Azure DevOps project, then go to Pipelines > Releases.
- Find the release definition you need to fix, click on it, and hit the Edit button to open the pipeline editor.
Step 2: Access the Agent Job Settings
- In the editor, select the stage that's failing to run (like "Development" or "Production").
- Inside that stage, click on the Agent job tile—it's usually the first item in the list of tasks for the stage.
Step 3: Switch to Your Local Agent Pool
- On the right-hand configuration panel, look for the Agent pool dropdown.
- By default, this is probably set to a Microsoft-hosted pool like
Azure Pipelines. Change this to your self-hosted agent pool (the exact same one your working builds use). - Quick check: Make sure the Demands section matches what your local agent supports. If your builds are already working, this should already be aligned, but it's worth a quick glance to avoid surprises.
Step 4: Save and Test
- Click Save at the top of the editor to lock in your changes.
- Trigger a new release to test it out. This time, it should use your local agent instead of the hosted one, so you won't hit that free minutes error anymore.
One quick heads-up: Before testing, make sure your self-hosted agent is running and connected to your Azure DevOps organization. If it's offline, the pipeline won't be able to pick it up, and you'll run into a different (but easier to fix) issue.
内容的提问来源于stack exchange，提问作者Larsi
