Posted by jpluimers on 2015/11/24
A while ago, I had this error on BitBucket:
Running git.exe with arguments "fetch --prune" failed with return code 128 and error output: "fatal: unable to access 'https://%email@example.com/%user%/%repository%.git/': Unknown SSL protocol error in connection to bitbucket.org:443
A quick search for “Unknown SSL protocol error in connection to bitbucket.org:443” pointed me to a comment by Ludwik Trammer on an answer by Jordfräs:
I resolved the issue by upgrading from git 1.8 to git 2.0.
Which reminded me this was a Windows system, where there is no package manager that verifies how far your non-system software is behind.
One day, I will write a script that finds out about the git version history and inform me of major/minor versions I’ve skipped.
Some notes for that:
Probably I will need to do something similar for Mercurial/hg in the future as well.
via: git – Unknown SSL protocol error in connection – Stack Overflow
Posted in Software Development, Development, Source Code Management, Power User, Windows 7, DVCS - Distributed Version Control, Windows 8, Windows, Windows Server 2008, Windows Server 2008 R2, git, Windows 8.1, Windows Server 2012, Windows Server 2012 R2, Windows 9 | Leave a Comment »
Posted by jpluimers on 2015/09/03
A while ago, we encountered this error when doing merges in TFS (non-GIT ones):
Microsoft Visual Studio
Source Control Merge Wizard
Merge encountered 1 error(s) and 0 warning(s).
First error/warning encountered:
Server was unable to process request. ---> Object reference not set to an instance of an object.
See output tool window for information on any other errors.
In the end this was caused by an out of disk space on the volume containing the TFS datastore.
Posted in Development, Software Development, Source Code Management, TFS (Team Foundation System) | Leave a Comment »
Posted by jpluimers on 2015/08/13
Besides commit statements from hg or git like this:
hg commit -m “fixes #6, resolve ticket #5 and see ticket #9 and ticket #5 in the tracker”
The best is to start with the command, then finish the comment (commands in the middle of a comment are far less reliable).
There is a whole bunch of commands for which BitBucket tries to understand conjugations of verbs:
You can also use the word “issue” in the middle to just link to an issue like this syntax:
links to issue #1
Finally, you can refer from issues to change sets using a cset syntax:
<<cset 2f2f8d4cae7da0e37a5ffbc81c527cb67cc56015>> where the hex number is from a URL in your commit list (for instance in https://bitbucket.org/jeroenp/fastmm/commits)
Note that linking from changesets to issues often automatically creates a back-link, but that doesn’t always work, and fixing it has very low priority (like many things on BitBucket): Issues getting linked to commits have the wrong link syntax, they show BB-6232 — Bitbucket.
Posted in BitBucket, Development, DVCS - Distributed Version Control, git, Mercurial/Hg, Source Code Management | Leave a Comment »