refs/changes/* not replicated to bitbucket

[Lior Gerenstein]

Hello,

I set up my gerrit server to replicate all changes in my project to bitbucket using HTTPS. 

I can get merged changes in any branch (master and others) to replicate just fine. However, standing changes which are waiting for code review, do not get replicated. On replication.log I see this line:

[2017-07-18 15:32:00,064] [] Push to https://***@bitbucket.org/***/***.git references: [RemoteRefUpdate[remoteName=refs/changes/12/12/1, NOT_ATTEMPTED, (null)...****, srcRef=refs/changes/12/12/1, message=null]]

I looked at the source code and it seems like NOT_ATTEMPTED means that "this ref is not configured to be replicated". Why is that the case? the documentation states explicitly that th e

    /** The ref is not configured to be replicated. */

    NOT_ATTEMPTED,

My configuration is very simple, I only define a remote url and project:

[remote "bitbucket"]

  url = https://***@bitbucket.org/***/${name}.git

  projects = ***

I also tried to specifically add a 'push' setting for refs/changes:

[remote "bitbucket"]

  url = https://***@bitbucket.org/***/${name}.git

  projects = ***

  push = +refs/changes/*:refs/changes/*

However, this had no affect.

Any ideas?

TIA

[diptim...@appdynamics.com]

It is not possible to replicate the open changes, but some expert must confirm this. 

[Luca Milanesio]

On 25 Jul 2017, at 09:04, diptim...@appdynamics.com wrote:

It is not possible to replicate the open changes, but some expert must confirm this. 

Who said that? We do replicate *all refs*, including open changes (refs/changes/*) and project configuration (refs/meta/*).

I have personally tried with Stash and works, with GitHub works, with BitBucket.org haven't tried yet, but there are no reasons for not to work, unless Atlassian have installed some hooks to prevent pushing non standard refs.

Luca.

--
--
To unsubscribe, email repo-discuss...@googlegroups.com
More info at http://groups.google.com/group/repo-discuss?hl=en

---
You received this message because you are subscribed to the Google Groups "Repo and Gerrit Discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to repo-discuss...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[diptim...@appdynamics.com]

Ah, I was not aware of this one. Thanks for the update :)

[Lior Gerenstein]

Apparently my reviews were replicated to bitbucket, but I did not see them on bitbucket UI, since the UI only shows branches which are pushed under refs/heads/*, while gerrit reviews are pushed under refs/changes/*.

I solved this by adding this line to replication.config:

push = refs/changes/*:refs/heads/review/*

This turns the gerrit change branches into 'real' branches which are displayed on bitbucket UI and can be easily accessed.