Considering a Migration from ClearCase to Git, Gerrit or Subversion?

Git

Open Source Software offers compelling benefits, including affordability, security & stability, speed of innovation and flexibility.  This especially is evident with OSS source code management software such as Git and Subversion. In this Webinar we will provide a proven framework to guide your decision – when to move, and if OSS is the right answer. We will present a proven path for migration from ClearCase or other proprietary SCM systems that has helped over 30,000 users to make the switch. This webinar will present an actionable strategy, covering the phases of discovery and planning, and  a practical guide for the … LEARN MORE »

Summary of the first Berlin Gerrit Hackathon

Hacking the Gerrit

Between 8th and 12th of September 2014, first Berlin based Gerrit Hackathon took place. It was joined effort of CollabNet, Elego and Aservo to host it. Our event attracted 16 people from various companies, including four Gerrit maintainers. Here is full list of participants: Dave Borowitz (maintainer) (Google), David Pursehouse (maintainer) (Sony Mobile), Saša Živkov (maintainer) (SAP), Edwin Kempin (maintainer) (SAP), Sven Selberg (Sony Mobile), Gustaf Lundh (Sony Mobile), Khai Do (OpenStack / IBM), Christian Aistleitner (Individual), David Ostrovsky (Individual), Deniz Türkoglu (Spotify), Carlos Martín Nieto (Elego), Eryk Szymanski (CollabNet), Jacek Centkowski (CollabNet), Johannes Nicolai (CollabNet), Dharmesh Sheta (CollabNet), Dariusz … LEARN MORE »

Gerrit Hackathon in Berlin next week

gerritcollabnet

Working in a distributed team has many advantages. You can work from any place in the world and any hours you would like to. Asynchronous communication over email or Gerrit Code Review is not as distracting compared to being poked by colleague from the desk opposite to you. Some people are most productive in the middle of night, others early morning (I mean really early morning like 4 or 5am). Forcing them to work from 9am to 5pm could kill their productivity. This is why many Open Source projects are so successful. People can do their work when they want … LEARN MORE »

You shall not pass – Control your code quality gates with a wizard – Part III

Gandalf

You shall not pass – Control your code quality gates with a wizard – Part III If you read the previous blog post in this series, you should already have a pretty good understanding on how to design your own quality gates with our wizard. When you finish reading this one, you can call yourself a wizard too. We will design a very powerful policy consisting of quite complex quality gates. All steps are first performed within the graphical quality gate wizard. For those of you who are interested in what is going on under the hood, we will also … LEARN MORE »

You shall not pass – Control your code quality gates with a wizard – Part II

Gandalf

You shall not pass – Control your code quality gates with a wizard – Part II In the previous blog post you learned how to select, test and deploy predefined quality gates with CollabNet’s code quality gate wizard for Gerrit. Those quality gates will make sure that all conditions regarding code quality and compliance are met before a commit can be merged into your master branch and trigger a pipeline that will eventually promote it into production. In this blog post we will focus on how you can define quality gates by yourself, using a methodology very close to setting … LEARN MORE »

You shall not pass – Control your code quality gates with a wizard – Part I

You shall not pass

You shall not pass – Control your code quality gates with a wizard Now as easy as designing an email filter Every project has different policies defining when code can be pushed into production. CollabNet’s code quality gate wizard for Gerrit comes with a bunch of predefined policies and lets you graphically design your own quality gates as easy as defining email filter rules. Four-eye peer review, legal has to approve copyright file changes, senior staff has to approve the work of juniors, democratic feature voting? – Regardless of what your code quality gates look like, chances are very high … LEARN MORE »

Implementing Gitflow with TeamForge and Gerrit Part III – Alternative approaches.

gitflow3

In this blog post series we talk about access right mappings between TeamForge and its Gerrit integration. The topics covered by each part are: in Part I: What Gitflow is, and how to best use it with TeamForge/Gerrit user defined repository policies in Part II: How to implement your own user-defined repo category with branch based permissions in TeamForge 7.1. in Part III: Alternative approaches to implement branch based permissions (without user-defined repo categories) and when to use which approach. Target audience: Project admins, Gerrit administrators using our TeamForge integration. In the first part of this serie, we have looked … LEARN MORE »

Introducing TeamForge Project Scope into Gerrit – Welcome to cross repo dashboards and RBAC

gerritcollabnet

If you ever wondered how you can see Gerrit change requests of different repositories but same TeamForge project in one dashboard/report you can assign custom Gerrit access rights to project role so that they apply to all Git repositories within the same TeamForge project you can make a Git repository visible to all project members of this TeamForge project but not to all members of the entire site (default access permissions) … read on. Fortunately, our blog posts are not just a one way street, unidirectional information broadcasting mechanism. We are listening to your comments and will turn your feedback … LEARN MORE »

GitEye and Interactive Rebase

Introduction As I mentioned in my earlier blog, TeamForge for Gerrit, a Gerrit patch set must be associated with one and only one commit.  In this blog I will talk about how you can commit your work periodically as you work on your change request and later use the interactive rebase feature in GitEye to squash your commits into one commit, and to compose a commit message suitable for Gerrit. The Scenario I have cloned a TeamForge Git repository and configured it for Gerrit as described in my earlier blog.  Also following the steps described in the earlier blog I have created and checked out … LEARN MORE »

TeamForge for Gerrit- Ready for the Enterprise

enterprise Gerrit

Git, Gerrit and TeamForge In this blog, I will show you how to use GitEye with Gerrit, the most widely used code review and permissions management framework for Git.  Although GitEye will work with any Gerrit server, I will be using TeamForge for Git.  TeamForge extends and wraps Gerrit, adding centralized role-based access control (RBAC) and greatly simplifying management of Gerrit access rights.  It also provides powerful features such as history protection, making Git ready for the enterprise. TeamForge Git Repository Configured for Optional Review TeamForge Role-Based Access Control Clone Repository The first thing I will do is clone my TeamForge Git … LEARN MORE »