If You Like ClearCase – You Belong in a Mental Institution

Watching a Google presentation by Linus Torvalds on GIT.
http://www.youtube.com/watch?v=4XpnKHJAok8

He disparaged CVS and other SCC systems, but since CVS is a step up from ClearCase, well – his comments are in spades…
BTW – Google uses Perforce…

Another person talking about ClearCase and why it is a tool from the 1970’s.
http://www.aldana-online.de/2009/03/19/reasons-why-you-should-stay-away-from-clearcase/

BTW – what other “tool” requires a dedicated administrator?
I administer a Perforce server used by 2 development groups (42 people).  It consumes about 5 minutes a month of my time.  It’s straight-forward and obvious – what more can I ask for.

Someone with a love/hate relationship with ClearCase:
http://clearcase.weintraubworld.net/

Gawd I HATE ClearCase

My God – I absolutely HATE ClearCase.

Not the mild dislike that I hold for lesser tools like “Visual Source Safe” or even “Lotus Notes”, but pure head-throbbing HATE.  Starting with the goofy jargon (‘discordance’ – I get it, you bought a thesaurus – get over yourself) and the sloooooooow cycle times.
Even the “atomic commit” that was NOT quite “atomic” – heh – that made for head-shaking stories as we commiserate…

But losing fracking files!

I’m just glad I have screen-shots of my latest deliverables so my bosses (who just love CC with wet sloppy kisses) will think my code still exists (while I resurrect it like some poor Cylon or …).

My hate for ClearCase rises from the pit of my stomach.  A rush of burning bile that blinds me with rage.
The hate washes over my soul wiping out all thoughts of redemption or even my normal “look at it from their perspective”.
No – the hate for this mere “tool” – is unprecedented for me.

I have disliked, jeered, and even scorned many things in life and work.
But ClearCase is the first thing in heaven or earth which has given me knowledge of true HATE.

</RANT>

Someone once said that ClearCase is like “Lotus Notes” – a joy if properly administered and with the correct user training.
Riiiiiiiight – well – I may truly dislike Lotus Notes – but ClearCase – I HATE.

Someone else also said that a lot of ClearCase issues would be solved with a “…for Dummies” book.  I have no pride and I would gladly pick up a “For Dummies” book – it’s just that none exist – and there is no market.
90% of the ClearCase user’s have been so brainwashed in the “beauty” of VOB’s and not needing a clear idea of a consistent “check-in package” – well there is no market.
(here I go again – other tools have the concept of a “change list” or “check-in group” – nope – not in ClearCase – you may have an aggregated check-in – but try finding the ‘related’ files a year later… OY)

Remember – I have 35 years experience in software on many many systems using a variety of SCC systems .  I have used “xcopy” to “winzip” to various commercial (both good and bad) and even CVS, but now that I have to use ClearCase in a multi-site project – well – you may understand the source of my rage…

—— UPDATE ——

Our friendly ClearCase administrator (3,000 miles away) fixed the lost files issue.  My configuration was “not quite right” and I was not really working with the branch that I thought I was working with.  Of course, this took more than an entire day to find and fix.
He was understanding, apparently this happens occasionally with “new folks”…
I am still thinking that the obvious nature of something like Perforce would make this a non-issue.

Of course – I still dispise using ClearCase…
++rls;

File.New behavior with SCC in PowerBuilder.NET

Question:
What happens when the library (PBL) is not checked out, and I try “File → New” ? Or more generally, how does “File→ New” interact with Source Code Control systems…
Short Answer:
The “File → New” action may fail, depending on how “automatic checkout” is set.
The attached document (PB125_SCC_Note1.pdf) contains the three scenarios for how “Automatic Checkout” may be set along with screen shots of the (current) behavior in PowerBuilder.NET.
The test case is for Microsoft’s Team Foundation Server (TFS) but everything should be the same for other SCC providers.
(Originally published 17 February 2011)

PowerBuilder.NET – SCC with VSS and Perforce

PowerBuilder.NET (here the shipping 12.0) can easily use most (all?) Visual Studio compatible source code control (SCC) providers.  The attached document shows the steps to connect to either  my personal favorite, Perforce, or Microsoft’s Visual Source Safe (which I believe is being discontinued by Microsoft in favor of TFS).

These SCC packages are easier than Microsoft Team Foundation Server (TFS) both because they are just SIMPLER, but I also did not need any extra adapter installed. Especially Perforce, IT JUST WORKS.
So, grab this older document (PBNET120_SCC_Instructions_Public.pdf), written back in the 12.0 timeframe, and party-on!

And, since I just love pictures, here’s a pretty and informative (looks and smarts) screen capture showing some details when the user adds a new global function and a text file.  The “project” files for the target and library are automatically checked out also…

PB120_PendingCheckins

(Originally published 13 February 2011)

PowerBuilder.NET SCC with TFS

PowerBuilder.NET (here version 12.5) can easily use Microsoft’s “Team Foundation Server” (TFS) for all the expected Source Code Control (SCC) actions.  PowerBuilder.NET, like any non-Microsoft product will need an adapter layer, which is provided by Microsoft free of charge.  The “Microsoft Source Code Control Interface” (MSSCCI) provider is the adapter providing the actual connection to the Team Foundation Server.

The attached document outlines the installing and an overview of using PowerBuilder.NET (and a little TFS) for the basic SCC needs.

The end result, is that you can double-click a file (like a window object), the file (and the hidden XAML mate) will be automatically checked out, put into the pending check-ins list, and the world is sweet.  Check out this attached PDF document (PB125_SCC_Overview_TFS.pdf) for the details.

PBNET125_TFS2

 (Originally published 3-February 2011)