Cloud Manager Code Quality Pipeline will not trigger on push of new commits | Community
Skip to main content
J
johnagordon83-1
April 17, 2025
Solved

Cloud Manager Code Quality Pipeline will not trigger on push of new commits

  • April 17, 2025
  • 2 replies
  • 661 views

In Adobe Cloud Manager we have the ability to create Code Quality Pipelines that can be configured to automatically trigger when new commits are pushed to the specified branch.  I have configured such a pipeline as seen below.

The problem I am experiencing is that when I push new commits to the branch in question, the pipeline is not triggered.  I can confirm that the new commits are successfully reaching the Adobe repository.  I can also confirm that we are using an Adobe repository and not a private one.

 

 

Can you offer any ideas why our code quality pipeline is not triggering on code pushes?  Thank you.

 

 

Best answer by SantoshSai

Hi @johnagordon83-1,

That's really strange! Could you confirm: 

  • Double-check that the pipeline is correctly associated with the exact branch you're pushing to. Sometimes it might be case-sensitive, or small typos in the branch name (like develop vs Develop) can prevent it from triggering.
  • Try triggering it manually once and then commit again to see if it restarts the auto trigger.

Note: Even though you're using an Adobe Git repo, make sure that webhooks are properly set up behind the scenes. Normally Adobe handles this, but in rare cases the webhook might not be firing or has gotten misconfigured. Opening a ticket with Adobe Support can help clarify if the hook is correctly firing when new commits are pushed.

 

Hope that heps!

Regards,
Santosh

2 replies

SantoshSai
Community Advisor
SantoshSaiCommunity AdvisorAccepted solution
Community Advisor
April 17, 2025

Hi @johnagordon83-1,

That's really strange! Could you confirm: 

  • Double-check that the pipeline is correctly associated with the exact branch you're pushing to. Sometimes it might be case-sensitive, or small typos in the branch name (like develop vs Develop) can prevent it from triggering.
  • Try triggering it manually once and then commit again to see if it restarts the auto trigger.

Note: Even though you're using an Adobe Git repo, make sure that webhooks are properly set up behind the scenes. Normally Adobe handles this, but in rare cases the webhook might not be firing or has gotten misconfigured. Opening a ticket with Adobe Support can help clarify if the hook is correctly firing when new commits are pushed.

 

Hope that heps!

Regards,
Santosh

Santosh Sai
    J
    johnagordon83-1Author
    April 18, 2025

    Thank you for your reply SantoshSai.  Manually triggering the pipeline before attempting to automate it didn't work, but I will open a ticket to resolve the issue.

    sarav_prakash
    Community Advisor
    sarav_prakashCommunity Advisor
    Community Advisor
    April 18, 2025

    Hi @johnagordon83-1 , one issue we ran into. 

    • We have 2 Program Orgs
    •  
    • Initially we configured single Adobe repo and reused in both our Orgs. 
    • When Git push happened, it triggered pipeline from one Org. But did not trigger pipeline at the second org
    • To workaround, we had to create second adobe repo, use Jenkins to remote sync code from first repo into second.

    Thereby incase you are using single adobe repo against multiple programs, only one pipeline gets triggered. Need to setup separate repo for each program

    J
    johnagordon83-1Author
    April 18, 2025

    Thank you for your response sarav_prakash, but we only have one program.

    Terms & ConditionsAccessibility statement

    Loading footer...