I have a drone.io account, offering me the possibility to have automated builds for my Go project that I host in a Bitbucket Mercurial repo. This works fine when I push changesets to the repo from my local machine.
But when I do a local commit on the Bitbucket site, the Post hook for the drone.io CI is not fired.
Is that a shortcoming, and so should I register a bug? Or is there a reason behind this behaviour?
This problem is solved with the solutiob provided thru Atlassian issue 9187.
Thanks very much for the good work.
I tried again, to no good. The local commit (1a853ccf1632) did not trigger a drone.io build. The last build on drone.io shows the one for cset 88dd6249717e. This concerns my public repo bitbucket.org/gohg/gohg, if you wonder. I tried it with another repo of mine, also configured with drone.io, and it has the same problem.
In case you should follow the drone.io button in the overview page of the gohg repo, you will see a (failed) build on drone.io for cset 1a853ccf1632. But that is one I just triggered manually from the drone.io site itself, for testing something there.
Just to make sure you're not confused by that build :) .
(I'll ask the guhys at drone.io if they could mark manual builds as such.)
I tried the test with http://posttestserver.com, but the result is the same. All goes well when I push changes to the different repos, but a commit after editing in the browser on the Bitbucket website does not trigger any POST hook.
So to me it is clear that neither the repo (I tried two different repos) nor the called services (I tried two different services, one of which recommended by the document you referenced) are the cause of the issue.
Maybe it could indeed be something with the Bitbucket POST hook not firing after a commit from the Bitbucket website?
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG