I'm a pretty big skeptic, so when they came to me to write a troubleshooting guide to help developers with their Git issues, I said great -- but would it really help? Would it solve enough of the problems to be useful? Would it address issues in the customer's landscape?
I wasn't sure, but I wrote it. I needed the money.
Then something amazing happened.
The Proof Is In the Pudding
I was setting up an account to do a demo of our new Gerrit pane (see the blog). All was fine, and I was confident, I had a done this a million times. I opened up SAP Web IDE, selected Git | CloneRepository, entered my URL, even clicked the Gerrit checkbox, and pressed OK.
Then it happened. I got this error message.
Whatt!!?? I've worked with Git a little, even in Git Bash, but what does "Cannot open git-upload-pack" mean? I have to admit: I was stunned and not sure what was wrong. I had butterflies in my stomach...the bad kind of butterflies.
Would it have the error I was getting? I searched for the word "pack", hoping I'd get a match. And there it was.
The exact error I was getting. Not only that, but it knew exactly what the problem was -- that I had forgotten to install the cloud connector to get access to my Git system inside our company (Git on-premise). The information was accurate, specific, and even had a link to the instructions for setting up connectivity to my Git system.
The rest is history. I installed the cloud connector (which wasn't as difficult as I feared), opened a channel to my Git system, created a destination ... and my clone worked.
I must give kudos to michal.keidar, who pushed the idea of troubleshooting guides (there's another for deployment and maybe others to come), as well as yossi.balan and tomer.epstein for developing the content for the Git troubleshooting.
If you have any ideas for troubleshooting guides or content, or anything dealing with training or documentation, let me know.