On Thursday, October 30, 2014, Ondrej Wisniewski <
ondrej.wisniew...@dektech.com.au> wrote:
> Hi Stefano and Dolph,
>
> since me and my team joined the OpenStack developer community just
> recently, I really appreciate your comments and suggestions. After all, we
> are here to learn. The current w
Thanks Ricardo for your suggestion about GitLab. I am looking into this.
Ondrej
/On 10/30/2014 09:20 AM, Ricardo Carrillo Cruz wrote://
/
Code review is a vital part of the Openstack CI workflow, and as such
the git repos managed by Openstack CI Gerrit are the authorative sources.
It looks to
Hi Stefano and Dolph,
since me and my team joined the OpenStack developer community just
recently, I really appreciate your comments and suggestions. After all,
we are here to learn. The current workflow we've set up might be a
consequence of a different development model we were used to. Anyw
Code review is a vital part of the Openstack CI workflow, and as such the
git repos managed by Openstack CI Gerrit are the authorative sources.
It looks to me you don't want to have Gerrit to be the authorative git
server to avoid doing code reviews in experiments or to share code among
developers
On 10/29/2014 07:02 AM, Ondrej Wisniewski wrote:
> If I understand correctly, we cannot use the OpenStack community Git
> servers as our central Git repository since developers cannot push to
> them. And we don't want to go through Gerrit and the code review
> procedure just to share a bit of code
On Wednesday, October 29, 2014, Ondrej Wisniewski <
ondrej.wisniew...@dektech.com.au> wrote:
> Hi Dolph,
>
> I guess it sounds complicated but in the end our setup is really not much
> different from the community workflow, a least this is the intention. What
> I am trying to achieve is a possibi
Hi Dolph,
I guess it sounds complicated but in the end our setup is really not
much different from the community workflow, a least this is the
intention. What I am trying to achieve is a possibility for the team of
developers to share code among each other by using a central Git
repository. T
On Wed, Oct 29, 2014 at 4:20 AM, Ondrej Wisniewski <
ondrej.wisniew...@dektech.com.au> wrote:
> Hi Ricardo,
>
> thanks a lot for your help and detailed instructions. It will surely come
> in handy when I will need to do something like that. I am looking also into
> this possibility.
>
> But the a
Hi Ricardo,
thanks a lot for your help and detailed instructions. It will surely
come in handy when I will need to do something like that. I am looking
also into this possibility.
But the actual reason I need to sync our central developer repo with the
Gerrit repo is a problem when the devel
I think what you are trying to achieve is to have a branch that tracks
upstream for the upstream projects, and another branch that tracks local
development in your Gerrit project.
You may want to check Jeepyb:
http://ci.openstack.org/jeepyb.html
That tool is what Openstack CI uses to manage gerri
Hi Cédric,
I have basically two internal OpenStack mirrors (bare Git repositories).
One is to share code contributions among the dev team members, the other
is handled by Gerrit and this is where the devs send code for review.
Both should be updated periodically from the upstream servers. Whil
Hi Ondrej,
Could you clarify your needs?
If you allow your devs to commit code on your local gerrit,
then your repo will differ from OpenStack one
and you might have merge troubles when you will resync your repo with
OpenStack one
How will you handle them?
Cédric/ZZelle
On Mon, Oct 27, 201
Hi Riccardo
thanks for pointers you provided. I had a look at the Gerrit replication
feature and the description says:
"/Gerrit can automatically push any changes it makes to its managed Git
repositories to another system./"
What I need would be exactly the opposite. I need to update the Gerr
Hi Ondrej
The replication between Gerrit and git mirrors is done by the Gerrit
replication mechanism.
If you look at this line in the gerrit manifest:
http://git.openstack.org/cgit/openstack-infra/system-config/tree/modules/gerrit/manifests/init.pp#n255
you will see that it deploys a 'replicati
14 matches
Mail list logo
