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 »

Agile Leadership Workshop – More Answers from the Expert

Over the past two weeks I have been fortunate enough to be allowed to run 5 workshops on Agility in general. While these have been sales or marketing funded, I was allowed to run them without any interference and we were able to come up with some great interaction and engagement. One thing I did promise to each workshop was that any question I couldn’t answer during it I would type up and send out in a follow up email. Below is a collection of all the unanswered questions I was able to gather, I hope I didn’t lose any, … 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 »

Grasping Agility; Hardening Sprints: A Fat Free Candy!

0ZrZMy0

I wanted to start off this blog with a succinct definition of “Hardening Sprint” so we are all on the same page. I couldn’t find one. I found a lot of words on the Scaled Agile Framework site that talk about and apparently justify Hardening Sprints if you want to read that. I decided to work up a quick definition of a “Hardening Sprint” myself: A pre-planned iteration in which we will do all the things we should be doing all along, but won’t. I’m reminded of a particular label that is very common on candy in stores these days. … LEARN MORE »

CloudForge’s Improved Subversion Service

The Backstory Since joining the CloudForge Development team within CollabNet nearly a year ago, several of my colleagues and I have been primarily focused on delivering improvements to the scalability and reliability of the CloudForge improved Subversion service.  With tens of terabytes of live Subversion repository data being generated and used by tens of thousands of our customers, even the smallest improvements we make to the service have a pretty big impact. CloudForge was built on a strong Subversion architecture, but over the years the ever-growing number of customers put a strain on the platform.  In the original architecture, customers (organizations) were … LEARN MORE »

Gerrit Dependency Management with GitEye

Introduction In my earlier blogs, TeamForge for Gerrit and GitEye and Interactive Rebase, I showed you the basics of using Gerrit with TeamForge and GitEye.  I also delved into using interactive rebase to squash multiple commits into one so that you can push to Gerrit, creating a single Gerrit change.  In this follow up blog I will give you some tips on managing Gerrit dependencies. Pushing Multiple Commits to Gerrit In my blog GitEye and Interactive Rebase I showed you what to do if you have made multiple commits and now you want to create a single Gerrit change that combines them.  Let’s suppose, … 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 »

connect with CollabNet
   Contact Us
sign up for emails
looking for something
conversations

CollabNet: Webinar on Sept 4, 8-9 AM PDT #Git #Gerrit w/ #TeamForge: Secure, Scalable, Standards-Compliant for the Enterprise http://t.co/isogxQEowi
Date: 2 September 2014 | 7:00 pm

CollabNet: Join #CollabNet founder + CEO, Bill Portelli to learn How To Scale #AppDev & Delivery across the Enterprise http://t.co/TLbhR6VGn2
Date: 2 September 2014 | 6:01 pm

CollabNet: RT @ccnim: Join us Thursday:"Git/Gerrit with TeamForge:Secure, Scalable, Standards-Compliant for the Enterprise"..Register at http://t.co/4…
Date: 2 September 2014 | 5:53 pm