`/azp run` can't start a pipeline if it is marked as `pr: none`

[sandreenko]

Azure Pipelines could not run because the pipeline triggers exclude this branch/path.

Originally posted by @azure-pipelines in #32362 (comment)

with /azp list you can get the list of the available pipeline, but if you try to trigger them you will see:
Azure Pipelines could not run because the pipeline triggers exclude this branch/path.
because they have that setting:

runtime/eng/pipelines/coreclr/ci.yml

Line 26 in 3216324

pr: none

So if we want to be able to trigger something with /azp run pipeline name we need to do the workaround from https://github.com/MicrosoftDocs/vsts-docs/issues/4206

[karelz]

@sandreenko only 1 area label please - see why

[ViktorHofer]

@trylek @safern do we know if this will change on the AzDO side? If not, I don't think this item is actionable and should be closed.

[trylek]

Well, so far I'm not aware of any indication that AzDO would be planning to roll out a fix / new functionality addressing this issue in the short term especially as this is kind of a feature request rather than a mere bugfix.

[ViktorHofer]

Can you please remind me why some pipelines like the one mentioned in the top aren't triggerable? How is this pipeline different from the libraries outerloop which is triggerable?

[sandreenko]

Can you please remind me why some pipelines like the one mentioned in the top aren't triggerable? How is this pipeline different from the libraries outerloop which is triggerable?

I think the task is:

1. trigger only a small amount of pipelines are when you run /azp run;
2. make all optional heavy pipelines triggerable with /azp run NAME;

right now if we delete pr: none from all pipelines when you do /azp run it will run them all, that is undesirable for jit GCStress jobs etc. that are taking hours and many machines. But with pr: none you can't get the second.

[ViktorHofer]

Isn't /azp run already a no-op in dotnet/runtime as we set the pipeline limit to 10 and we have more than that?

[safern]

I think if we just remove the PR triggers and then set the options on the UI that the pipeline requires a comment to run, it would solve this issue.

Isn't /azp run already a no-op in dotnet/runtime as we set the pipeline limit to 10 and we have more than that?

Yeah, this would happen and no pipelines would run, so I'm OK with removing the PR trigger section from the yml file.