Azure self hosted agent failing to pick up jobs - Stack Overflow

admin管理员组

文章数量:1244247

I am new to azure and ci/cd. I created a self hosted agent. I created the agent because I receive an error message

No hosted parallelism has been purchased or granted. To request a free parallelism grant, please fill out the following form

I was directed to create an self hosted agent. So I followed the steps and the agent is connected to the server and listening for jobs. I updated my yml file, looking at the error the new localAgentPool did pick it up. However I am getting the same error, no hosted parallelism has been purchased or granted. I do not know why I am getting that error since I am using self hosted agent. Also not sure what parallel jobs even is. In the pipeline section it has free parallel jobs 1 viewing parallel jobs it has 0/1 I don't need to run the jobs parallel. This is for a school project, I will only ever have one job running at a time.

trigger:
- main

pool:
  vmImage: localAgentPool

steps:
- script: echo Hello, world!
  displayName: 'Run a one-line script'

- script: |
    echo Add other tasks to build, test, and deploy your project.
    echo See 
  displayName: 'Run a multi-line script'

I thnk it's not choosing the correct pool?

Pool: Azure Piplelines Image:localAgentPool But I think it should be localAgentPool and image:localImage

I updated the yml to run without parallel but same no hosted parallelism error.

trigger:
- main

pool:
 vmImage: ubuntu-latest
 demainds:
   - parallelism: 1

steps:
- script: echo Hello, world!
  displayName: 'Run a one-line script'

- script: |
    echo Add other tasks to build, test, and deploy your project.
    echo See 
  displayName: 'Run a multi-line script

I am new to azure and ci/cd. I created a self hosted agent. I created the agent because I receive an error message

No hosted parallelism has been purchased or granted. To request a free parallelism grant, please fill out the following form https://aka.ms/azpipelines-parallelism-request

I was directed to create an self hosted agent. So I followed the steps and the agent is connected to the server and listening for jobs. I updated my yml file, looking at the error the new localAgentPool did pick it up. However I am getting the same error, no hosted parallelism has been purchased or granted. I do not know why I am getting that error since I am using self hosted agent. Also not sure what parallel jobs even is. In the pipeline section it has free parallel jobs 1 viewing parallel jobs it has 0/1 I don't need to run the jobs parallel. This is for a school project, I will only ever have one job running at a time.

trigger:
- main

pool:
  vmImage: localAgentPool

steps:
- script: echo Hello, world!
  displayName: 'Run a one-line script'

- script: |
    echo Add other tasks to build, test, and deploy your project.
    echo See https://aka.ms/yaml
  displayName: 'Run a multi-line script'

I thnk it's not choosing the correct pool?

Pool: Azure Piplelines Image:localAgentPool But I think it should be localAgentPool and image:localImage

I updated the yml to run without parallel but same no hosted parallelism error.

trigger:
- main

pool:
 vmImage: ubuntu-latest
 demainds:
   - parallelism: 1

steps:
- script: echo Hello, world!
  displayName: 'Run a one-line script'

- script: |
    echo Add other tasks to build, test, and deploy your project.
    echo See https://aka.ms/yaml
  displayName: 'Run a multi-line script

• azure
• azure-devops

Share Improve this question Follow edited Feb 18 at 3:34 newdeveloper asked Feb 18 at 2:32 newdevelopernewdeveloper 70477 silver badges2121 bronze badges 3

• Once again check your self-hosted agent is connected and showing as Online in the Azure DevOps portal under Organization settings > Agent Pools > localAgentPool > Agents. – Suresh Chikkam Commented Feb 18 at 3:34
• yes it is online. I even tried to run without parallel on azure default pools but no luck – newdeveloper Commented Feb 18 at 3:35
• Removed vmImage parameter when using a self-hosted agent because we use vmImage only for Microsoft-hosted agents. – Suresh Chikkam Commented Feb 18 at 3:41

Add a comment  | 

1 Answer 1

Sorted by: Reset to default 1

To specify the self-hosted agent pool, please use name in pipeline yaml. vmImage is only valid in the Microsoft-hosted pool.

pool:
  name: localAgentPool          #<--- use name

steps:
- script: echo Hello, world!
  displayName: 'Run a one-line script'

Add if you would like to use demands(fix the typo) to find specific agent, there is no such parallelism, you need to check the agent capability for the value.

Please refer to the doc for more details.

本文标签： Azure self hosted agent failing to pick up jobsStack Overflow