[Bug] Could not queue the build because there were validation errors or warnings.

[priscofarina]

I am trying to use the new version:

- uses: Azure/pipelines@v1.2
  with:
    azure-devops-project-url: 'https://dev.azure.com/organization/project-name'
    azure-pipeline-name: 'pipeline-name' # name of the Azure pipeline to be triggered
    azure-devops-token: '${{ secrets.AZURE_DEVOPS_TOKEN }}'
    azure-pipeline-variables:  '{"variable1": "value1", "variable2": "value2"}' # optional stringified json

but once I create the workflow in which I pass some variables I get the following message:

Error: Could not queue the build because there were validation errors or warnings.

Are those not supported yet?

Removing the following section from my workflow definition, the pipeline get triggered.

azure-pipeline-variables: '{"variable1": "value1", "variable2": "value2"}' # optional stringified json

[priscofarina]

Looking to other issues likie this: #38 it seems the common suggestion is avoid using those workflows, instead use the integration from the GitHub marketplace.

If this is the case I think would be better having those lines deprecated for a while, otherwise I think many issues with the same reason will be raised.

[schdief]

I think using the GitHub App is not a sufficient alternative, we use GitHub Actions to build a software that we want to test within different CI/CD tools, so our GHA needs to trigger Azure Pipelines directly, without any app, e. g. in order to fetch the results or instrument the run with variables like the version of our software to be tested

[Ant0Kr]

Hello! Thanks for the question.

I have the same problem, so I can't pass parameters to the Azure DevOps pipeline.

Is anybody gonna fix it?
Is there any workaround for this?