Feature Hat-trick: Three new Git features for TeamForge in a week

hattrick

The rule of three The rule of three also seems to apply to new TeamForge Git features. Last week, I blogged about the top three Git features coming with the new TeamForge 8.0 release.  In the same post, I already announced that another three Git features will be released immediately after the launch, so let’s inspect how this hat-trick looks like.   1. Assign an entire TeamForge Team to a Code Review with One click TeamForge 8.0 introduced teams as a native concept. If you like to add all team members to a Gerrit change (Git Code Review) at once, you can …

Read More »

Top 3 Git Features coming in TeamForge 8.0

gerritlogo

CollabNet just released TeamForge 8.0 and with it some significant new features for our Git/Gerrit integration. Without further ado, let’s have a look into the top three. Define Git permissions globally: Site-wide role support for Gerrit As described in detail in my previous blog post, TeamForge project roles control access to all tools integrated in your development process, no matter whether you use Git, Subversion or both, how many servers you use or what your favorite issue tracker is. What happens if you like to define permissions across TeamForge projects on a global basis? Let’s say you have a group …

Read More »

Effective SCM Strategy for the Modern Enterprise

Recently CollabNet published the new whitepaper “Effective SCM Strategy for the Modern Enterprise“, which discusses issues that large companies face when working on their Software Delivery Lifecycle (SDLC) infrastructure. While understanding the requirements for repository management is a major part an enterprise IT strategy, when we talked to our customers and prospects, we noticed an interesting (and somewhat troublesome) trend in how people view SCM technology. The key problem we were seeing is that software configuration management (SCM) is typically viewed as a merely technical issue. Business stakeholders often completely rely on the technical experts – users of the SCM …

Read More »

Enterprise Agility and CollabNet

I recently had the good fortune to get on the road for a few weeks and take a deep look into both the state of software delivery and the role CollabNet plays in the industry.  From recent meetings with our growing field sales force, to visits with global customers and partners in the U.S. and Asia, I am excited to see the alignment of our company strategy with actual market dynamics.  As a company that has always been agnostic to any tool or process, the reality of today’s software development environment is that it requires both flexibility and structure across …

Read 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 …

Read More »

Why compete? Embrace Git and Subversion in the Enterprise

Git and Subversion

I read a blog post this week in ReadWrite about how Git is giving Subversion a run for its money. The author states, “It has taken a long time for Git to push Subversion aside, despite clearly being better for developers.” My question is this…why does Git need to push Subversion aside and declare to be better? Comparing Git and Subversion is like comparing apples and oranges. Yes, they are both in the fruit family, but one is not better than the other. Git and Subversion are both version control systems (VCS) which allow developers to manage changes to documents, …

Read More »

Git Repository Replication with Gerrit and TeamForge

replicated

Update: Git Replication is now a built-in feature in TeamForge 8.1 Why do we need replication in general? There are several scenarios in which it is quite handy to have a repository whose version history is exactly the same as the one it mirrors. Perhaps the most obvious one is the maintenance of a simple backup repository, used when the primary repository has become inaccessible due to a hardware failure, network outage, or other annoyances. Other scenarios include deploying mirror repositories to distribute heavy load across multiple servers. We’re using Git, a DVCS. We don’t need replication. Do we? Depending …

Read More »

Repository Dictated Configuration — Part 3 of 3: Global Ignores

iprops

Global Ignores Welcome to the last topic in my three part series on repository dictated configuration (RDC).  In part 2 we talked about the new svn:auto-props property.  Today we’ll discuss the other new inherited property that involves RDC, svn:global-ignores. Ignoring Unversioned Items Before 1.8 Once again, this is just a quick refresher, if none of this sounds familiar, then give this section of the Version Control with Subversion book a quick read. Up until 1.7 there were two ways to prevent the svn add and import subcommands from adding certain items we didn’t want to place under version control (as …

Read More »

Repository Dictated Configuration — Part 2 of 3: Autoprops

iprops

Automatic Properties In part 1 I talked about the new inheritable properties feature in Subversion 1.8.  I promised that this feature would pave the way for repository dictated configuration (RDC).  Today I’ll show you the first part of 1.8’s RDC related features, the new svn:auto-props property. Wait…What is RDC Exactly? Subversion provides an extensive set of user configurable options which control various aspects of a Subversion client’s operations.  For repositories with only a small handful of committers in the same location, manually synchronizing these configurations is probably not too difficult.  For larger and/or distributed groups however, ensuring that everyone has …

Read More »

Repository Dictated Configuration — Part 1 of 3: Inheritable Properties

iprops

Bait-and-switch warning: Despite the title, I won’t talk about repository dictated configuration (RDC) today at any great length.  Rather, I’ll talk about the new inherited properties feature, which RDC is built upon, in the hope that it will provide a more complete understanding.  In part 2, I’ll move on to the details of RDC proper. Property Inheritance Even the most casual user of Subversion is likely familiar with versioned properties.  These name:value pairs of metadata are assigned to files or directories.  Some (those properties whose names begin with “svn:“) are attributed special meaning by, and trigger specific behaviors in, Subversion …

Read More »