nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Cant Trigger Dynamic Pipeline also on Merge

Ozan Kizildogan

Trying to trigger the dynamic pipeline intervention at merge...

After a pull request, it works alright:

Screenshot 2025-01-16 at 00.41.56.png

But when the PR is merge, it is no longer triggered.

See below image, not that "This pipeline is generated by dynamic pipelines" is missing:

Screenshot 2025-01-16 at 00.46.15.png

We need the dynamic pipeline to decide which runner to pick! Otherwise it has no use.

Any suggestions? Perhaps missing permissions scopes in the manifest.yml file?

Comments

Daniil Penkin

Hello @Ozan Kizildogan,

Dynamic Pipelines provider is called for every pipeline, there are no exceptions. However, the message "This pipeline is generated by dynamic pipelines" you referred to is shown only if the provider altered the configuration, i.e. the configuration it returned differs from the configuration it received as input.

I can see in our logs that your Dynamic Pipelines provider was called for the merge commit in question, 36950458c0e60a0e2af0d85ab1813313e2680fe3. So it looks like your provider responded with unchanged configuration to that request.

Hope this helps. Let me know if you have any questions.

Cheers,
Daniil

Ozan Kizildogan

Hello @Daniil Penkin ,

Thanks for checking the logs. This clears my doubts on whether the dynamic pipeline is triggered at merge.

I have now another question about comparing the difference between the approved PR against main. Equivalent to running