Johannes Nicolai

About Johannes Nicolai

Johannes Nicolai is CollabNet’s Development Manager leading all Git and Gerrit related development efforts. Furthermore, he is responsible for CollabNet Connect /synch, CollabNet’s platform to integrate TeamForge with third party ALM platforms. Johannes holds a Master of Science in IT Systems Engineering from Hasso Plattner Institut Potsdam and is a Certified Scrum Master. Before joining CollabNet five years ago, he was doing consulting on user centric design, developing cryptographic software and architecting SAP integrations. He is an Open Source enthusiast and contributes to many projects (check out https://www.ohloh.net/accounts/10619 for details).

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 …

Read More »

The lean SyncUp – How Today’s ALM Architects Use CCF 2.3 to Create Radically Successful Bidirectional Synchronizations of Quality Center and TeamForge Requirements

ccf

Introduction Stop me if you’ve heard this one before. You have multiple ALM platforms and development point tools that all have to work together. You decided for a data synchronization approach so that you can benefit from unified reporting, save license costs and still enable all stakeholders to use their favorite tools with their favorite platform while having access to the full data. The pilot goes well, demonstrates the benefits you hoped for and you decide to go in production. For the first projects you sync, things work out as planned but the more projects you add, you feel the …

Read More »

CollabNet Git History Protection – Yet another public proof why it is badly needed

Git-secure-lock-300-px1

Yesterday, a developer accidentally reset the content of 186 Git repositories of the famous Jenkins project on GitHub. The content of those repositories got reset to an older version with no possibility to restore from remote without knowing the latest valid content. In contrast to many other version control systems, Git has a force push option which allows you to change the history of repository in a non linear way, i.e. with no possibility to just go back to the previous commit to restore history. In a similar fashion, it is possible to remove entire branches without a possibility to …

Read More »

Customer first: Welcome to CCF 2.2.1

ccf

What to expect from a point release of CollabNet’s Software Lifecycle Integration Platform (CCF)? That it has been sucessfully qualified against all available synch plugins (TeamForge, HP Quality Center, MS Team Foundation Server, ClearQuest, Jira, Scrumworks Pro, …)?  – Definitely That it plays very well with the brand new look and feel of our newest member of supported synch plugins – TeamForge 7.0? – Sure That it fixes bugs encountered in previous releases? – No big deal So it is no surprise that CCF 2.2.1 delivers all this – official support for TeamForge 7.0, bug fixes and a couple of …

Read More »

Security fix for Gerrit – Please update your TeamForge Git Integration if you use branch based permissions

Git-secure-lock-300-px1

This week, we learned about a security problem in core Gerrit related to read related branch based permissions. The original issue can be found here. If you do not use branch based read permission on your Gerrit server, you are not affected at all. The default repo categories configured with TeamForge do not use those, so as long you do not have any repositories using the custom repository category, there is no issue at all. If you are using the custom repository category and have configured read branch based permisisons, it is possible under certain conditions ( iff the atacker …

Read More »

Taking Software Lifecycle Integration (SLI) to the Next Layer: Welcome to CCF 2.2

ccf

CCF aka CollabNet Connect /synch has been CollabNet’s Software Lifecycle Integration (SLI) solution to seamlessly connect various tools with our ALM platform TeamForge for quite a while already. Over the years, its architecture evolved from a local Windows-only client, to a stable, distributed, platform independent solution. CCF has always been Open Source and defined a common artifact data model from the very beginning.  The steps how to write your own synchronization engine are well documented, and we have quite a selection of community integrations, among them MS TeamFoundation Server, Atlassian Jira, Rational ClearQuest (and of course our officially supported integrations …

Read More »

Spring Awakening – New Look and Feel for Our TeamForge Git Integration

New Look&View for our Git Repo Browser

As Spring finally arrived in town, we thought it’s time to give our Git repo browser a fresh new look and released a new point upgrade of our TeamForge Git Integration.   Apart from the fresh look, we also took this opportunity to fix some bugs reported in the last quarter. For further details, please refer to our release notes. If you dig deeper, you will figure out that we also added some more features to our repo browser, namely blaming support for changed files, gravatar support and linkification for TeamForge artifacts. If your commit message or file content contains a reference …

Read More »

BED Time Stories – Sharing Gerrit, Jenkins and Eclipse Knowledge

BED - Berlin Expert Days

We had a really great time on BED – Berlin Expert Days last Thursday and Friday. The conference was very well attended – we heard about 700 participants – and the talks gave invaluable insights into what’s hot in Java, DevOps, NoSQL and everything related to it. Among many other things we learnt how SoundCloud scales (technically as well as organizationally, Ruby has already crossed its peak as new stuff is written in Scala), why Adam Bien typically removes 60 percent of production code on his gigs and how ImmobilienScout24 managed to establish a DevOps culture by encouraging every single …

Read More »

Latest GitHub incidents show Git History Rewrite is both Day and Night for Enterprise Compliance

Git-secure-lock-300-px1

It did not take a full day before GitHub had to disable its recently announced source code search feature again. The reason for that is perfectly explained in this blog post on arstechnica. In a nutshell, many users had uploaded Git commits to public GitHub repositories which contained confidential information, including their private keys (cryptographic credentials). Everybody who knows how to search for those private keys could use GitHub’s code search and log into major production sites. This is definitely not GitHub’s fault but a critical oversight of the repository owners who uploaded confidential credentials to a public repository. You …

Read More »

New feature in CollabNet Connect /sync (CCF): Reverse field mappings automatically and save 50 percent of your time

reversefieldmapping

There is one CCF feature request from our customers, we are hearing over and over again:  “Setting up field mappings from <your third party ALM tool here> to TeamForge takes a lot of time, isn’t there any way to at least semi-automate this?” In particular, people wondered if they already designed their field mapping rules from Quality Center to TeamForge, why they cannot just generate the mapping for the opposite direction. While our hands were tied with custom field mappings and Altova MapForce (automatically reversing expressions in a Turing complete language [XSLT] is technically impossible), we kept this use case …

Read More »