Team CollabNet

About Team CollabNet

Top 3 Git Features coming in TeamForge 8.0

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 »

TeamForge Git-Integration 8.2.1 adds more federated RBAC to Gerrit

We are proud to announce and release version 8.2.1 of our Git/Gerrit integration with TeamForge today. This version exposes even more federated RBAC (role base access control) capabilities of TeamForge within Gerrit. What do I mean by federated RBAC? There is just one central place (TeamForge) where you can define permissions for all tools of your software development tool chain. For example, when a new employee joins your company as a developer, you have to create their account in TeamForge and automatically make sure that they can log into all connected tools like Gerrit, SVN, ReviewBoard, Trackers, Wikis, discussion forums, …

Read More »

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

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 …

Read More »

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

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 …

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

Read More »

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

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

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

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

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

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 »