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; } } }

Post Merge build trigger plugin to bamboo

Christopher Lefevre

I am using the Atlassian plugin Post-Receive WebHooks to call Bamboo to start a build on all commits. However when a Merge is done, the hook does not trigger.

In searching for an answer I found this question: https://answers.atlassian.com/questions/130202/post-hooks-unsuccessfully-triggered-after-clicking-merge-button-in-a-pull-request

Which there is a reply that explains that a plugin can be created that consumes the PullRequestMergedEvent object, but I have no idea how that would be done. I've found a couple of people discussing the issue, but not one implementation of a plugin to fix this issue.

The other question is the closest I've found to someone putting something together. I attempted myself but can't spend more time on this as it's already taken up days of my research and only let to brick walls.

Anyone have any advice on actual implementation, or even an example not unlike the Post-Receive WebHook plugin that works great, outside of this instance?

Accepted answers

Christopher Lefevre

Had to make a support ticket to try and resolve this.

All comments

cofarrell

Hi Chris,

This may be a dumb question, but which hook are you talking about. Unfortunately there are a couple. Are you talking about the one we just uploaded ot Marketplace recently?

That plugin, and most others I hope, should be implementing AsyncPostReceiveRepositoryHook which will listen for both Push and Merge events already. The advice from Tim is old and was before we introduced our new hook API.

Otherwise, is there anything in your $STASH_HOME/log directory that might indicate an error?

Cheers,

Charles

Christopher Lefevre

I just had time to start looking into this, thank you so much for the reply. Interesting that it should already be set up though.

I have no confirmed that we are using that plugin, with the Add-on key: com.atlassian.stash.plugin.stash-web-post-receive-hooks-plugin

Could not seem to find the Add-On key to compare on the page you linked, but I would think it a little absurd if they were different Add-ons.

I will investigate further into the logs and see if I can find something in there to report back soon.

Christopher Lefevre

So after further testing, it was found that the domain wasn't resolving properly.

However, we are using the "Gitflow Workflow" where you commit a new feature branch, then merge into a "Development" branch, then later merge to master. When doing this, it appears that if we merge to Master, the build is kicked off. However if we merge to development, the build is NOT kicked off?

Is this a known issue, or is there any tips that may fix this behaviour?

cofarrell

Hi Chris,

Honestly I'm not sure, I suspect this may be part of the problem:

https://answers.atlassian.com/questions/150470/why-commits-to-branch-trigger-build-on-master-and-not-branch

My quick reading on the subject I think Bamboo has slightly different Plan keys for branch builds, so a URL containing the main plan key won't trigger them.

A quick and dirty option would be to add another URL to the hook which has the plan key of the development branch build. If you need this to work for more than those two branches then this obviously won't scale and I suspect you'll have to enabling polling.

Sorry I can't be more help.

Charles

Perron Jones

Hi Chris,

I have a question pertaining to setting up the webhook plug-in.

What did you put as your URL for bamboo?

I see that we are supposed to include the path to the hook listener, but I'm not sure how to locate the hook listener for bamboo.

It would be great if you could let me know how to find the hook listener address.

Thank you,

Perron

Christopher Lefevre

You ned to set up your bamboo plan to react to repository changes, not polling. Then you need to use the REST API for triggering the build via the url:

http://<IP of your Bamboo Instance>:<Port>/api/rest/updateAndBuild.action?buildKey=<Build Key>

The build key can be found by looking at the URL of the plan you wish to trigger. For example mine ends with the URL: browse/STP-GFRT

STP-GFRT being the Build Key that we use.

For example, our internal version is:

http://192.168.254.10:8080/bamboo/api/rest/updateAndBuild.action?buildKey=STP-GFRT

Of note, we have the server set up to be at port 8080 and /bamboo

Christopher Lefevre

Had to make a support ticket to try and resolve this.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

bitbucket-server

bamboo

webhook