Azure Devops Service pipelines doesn't work

[distant sinew]

Hello!

I'm trying to run a simple pipeline in commit stage on main branch, with the following yaml script:

trigger:
  branches:
    include:
      - main
pr:
  branches:
    include:
    - main 

# Using Microsoft hosted-agent (managed by Microsoft)
pool:
  vmImage: ubuntu-latest

jobs:
- job: CommitStage
  displayName: 'Commit Stage for Task Service'
  
  steps:
  - checkout: self

  - task: Maven@3
    inputs:
      mavenPomFile: 'pom.xml'
      goals: 'clean install'
      javaHomeOption: 'JDKVersion'
      jdkVersionOption: '1.17'
      mavenVersionOption: 'Default'
    displayName: 'Build and Test Task Service'
    
  - script: curl -sSfL https://raw.githubusercontent.com/anchore/grype/main/install.sh | sh -s -- -b /usr/local/bin
    displayName: 'Install Grype for vulnerabilities scan'
    
  # Assuming the project to be scanned is at the root of the repo
  - script: grype .
    displayName: 'Vulnerability Scan with Grype'
    

The CLI output return the following error:

##[error]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
Pool: Azure Pipelines
Image: ubuntu-latest
Started: Today at 14:22
Duration: 2m 51s

I don't know what's that mean? I don't have any parallel jobs! it's just one script, and the docs says: it's free to use hosted agents!

help please

[viral cloak]

Have you followed the link in the error?

[distant sinew]

hi, yeah it wants me to submit a form and wait for 2-3 days

I don't want to do that , as my pipeline looks simple

[viral cloak]

is your project public or private?

[distant sinew]

i tried with both modes

no changes

it seems this pipeline is parallel

and i should switch to selfhosted agent

:/

[viral cloak]

appears that MS changed the default behaviour on newly created orgs for hosted agents due to abuse.

TLDR; People were using automation to spin up 1000's of Azure DevOps organizations, adding a pipeline and using the service to send spam, mine bitcoin or for other nefarious purposes. The fact that they could do so free, quick and without any human intervention was a burden on the team. Automatic detection of nefarious behavior proved hard and turned into an endless cat-and-mouse game. The manual step a necessary evil that has put a stop to this abuse and is in no way meant as a step towards further monetization of the service. It's actually to ensure a free tier remains something that can be offered to real peopjle like you and me,

https://learn.microsoft.com/en-us/azure/devops/release-notes/2021/sprint-184-update?WT.mc_id=DOP-MVP-5001511

[distant sinew]

🤦‍♂️

[viral cloak]

looks like your options are to run a private agent or fill out the form.

You could run a private agent whilst you wait for a reponse on the form I guess.

[distant sinew]

ahaa good idea

alright thanks

[thick vale]

Form is really easy, and they do reply within timeframe. Had to fill it a few weeks ago.