# Using git bisect to find a deployment-breaking commit

DevFeed: [Using git bisect to find a deployment-breaking commit](<https://devfeed.tech/articles/bisect-the-dragon-27288.md>)

Original publisher: [Read original article](<https://blog.pchudzik.com/201712/bisect-the-dragon/>)

Published: 2017-12-21T00:00:00Z

Content type: tutorial

Language: en

Sources: [Paweł Chudzik](<https://devfeed.tech/sources/pawe-chudzik.md>)

Topics: [Git](<https://devfeed.tech/topics/git.md>), [.NET Conf](<https://devfeed.tech/topics/net-conf.md>)

Tags: [debug](<https://devfeed.tech/tags/debug.md>), [deployment](<https://devfeed.tech/tags/deployment.md>), [git](<https://devfeed.tech/tags/git.md>), [jenkins](<https://devfeed.tech/tags/jenkins.md>)

## AI overview

This article explains how git bisect quickly identified a commit that broke a Jenkins deployment. The example traces the issue to a colon in MySQL test configuration system properties.

## Source excerpt

It all started on Friday, like many of the bad things that can happen in software ;) We've been working for some time and after being blocked with deployments for a long time (don't ask, you don't want to know ;)) we were finally able to deploy a new version. Our last release was about week ago. Do the deployment - seems like the easy thing to do. I've triggered deploy plan on Jenkins and it's failed. Here is the story how I've fixed something that looked like hours of analysis in few minutes. Read more