Low Summary
Automatic Fork Sync results in a qualified branch name (refs/heads/<branch>) instead of a short name in Remote Events
Steps to Reproduce
- Enable DEBUG logging on Bitbucket Server
- Set up a "SOURCE" repository in Bitbucket Server
- Fork the repository to a "TARGET" repository, ensuring Fork Sync is enabled
- Merge to the "SOURCE" repository
- Wait for Auto Fork Sync to trigger
- Check RemoteEvents logs
Expected Results
master sent to Remote Events as below:
2017-08-18 19:17:28,340 DEBUG [events.remote.ratelimit.threads:thread-3] c.a.e.r.impl.RemoteEventDispatcher Successfully dispatched events Set(com.atlassian.stash.plugin.remote.event.StashBranchChangedRemoteEvent@5d9d7fdc[branchName=master,repositoryProject=TESTING,repositorySlug=source,committer=testuser,sourceId=<null>,sourceUrl=<null>], ...)
Actual Results
We see that refs/heads/master is sent to Remote Events in the atlassian-bitbucket.log file:
2017-08-18 19:17:45,570 DEBUG [events.remote.ratelimit.threads:thread-2] c.a.e.r.impl.RemoteEventDispatcher Successfully dispatched events Set(com.atlassian.stash.plugin.remote.event.StashBranchChangedRemoteEvent@1bc9c280[branchName=refs/heads/master,repositoryProject=TESTING2,repositorySlug=target,committer=testuser,sourceId=<null>,sourceUrl=<null>], ...)
Workaround
You may be able to work around this by manually merging instead of using the auto-sync functionality.
- mentioned in
-
Page Loading...