search

1234- / gitblit

Automatically exported from code.google.com/p/gitblit
Apache License 2.0
1 stars 0 forks source link

New branches only propagated by replication after a commit #592

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
We are encountering what seems to us like an unexpected behavior of federation.

We have the following setup: a "master" and a "slave" gitblit instance. The 
slave is kept up to date using federation.

What steps will reproduce the problem?
1. Create a new local branch on a local repository, cloned from master.
2. Push the newly created branch to master.

What is the expected output? What do you see instead?
The newly created branch can be seen on the gitblit HTML interface of the 
master, but never on the slave (even after the federation delay).
As a workaround, we discovered that any commit on this new branch, when pushed 
on master, would lead to the branch appearing on slave.
We would expect newly created branches to be "federated" once pushed to master, 
without the need for a commit.

What version of the product are you using? On what operating system?
Both gitblit instances are v1.6.2 running under Windows Server 2008.

Original issue reported on code.google.com by olivier....@gmail.com on 22 May 2015 at 12:54

GoogleCodeExporter commented 9 years ago 
Ok, I see exactly how that happens.

I'll work on a fix.

Original comment by James.Mo...@gmail.com on 22 May 2015 at 3:50