Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,560,577
Community Members
 
Community Events
185
Community Groups

CI trigger is not working in azure devops for powerapp pipeline

CI trigger is not working in azure devops for powerapp pipeline

I have done changes in solution and click on publish customization but build not triggered

even I have enabled CI trigger button

 

1 answer

0 votes
Theodora Boudale
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Sep 21, 2022

Hi @Dev raj,

Are you using Azure DevOps with a Bitbucket Cloud repo? You don't mention anything about Bitbucket and I don't see a Bitbucket Cloud account in our system with your email.

In case you have a Bitbucket account with a different email and you use Azure DevOps with a Bitbucket Cloud repo:

Go to Repository settings for this repo in Bitbucket Cloud > select Webhooks, find the Azure webhook, select View requests for this webhook, and then select Enable History.

Then perform an action that should trigger a new build, and check if you can see the webhook request on the page where you enabled history.

If there is a request with status 200 this means the webhook works ok.

In this case, I would suggest checking the following doc from Azure DevOps for further troubleshooting:

https://learn.microsoft.com/en-us/azure/devops/pipelines/repos/bitbucket?view=azure-devops&tabs=yaml#i-just-created-a-new-yaml-pipeline-with-cipr-triggers-but-the-pipeline-is-not-being-triggered

If you still need assistance, I would suggest contacting the support team of Azure Devops.

Kind regards,
Theodora

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events