There are workarounds for that like using ClearCase Multisite scm DB replica technology , but you have to pay extra for it and is not trivial to adminstrate. Possibly the worst software ever made. I will not work for any firm that uses rational anything. Aside from CC completely crashing and restarting my workstation frequently on dynamic builds. What happens when you are pushing something to source control and CC does what it does best, crash?
No, it is gone forever. So if you are ever in the god-awful situation of using this giant piece of expensive software, keep duplicates of everything. Way to capture the most important part of source control, reliability. Die slow. The merge tool is not worthwhile. It barely helps you, remembers no decisions you made, its just a glorified diff. Its a bit insane. I use BitKeeper at work let's assume Git , and merging two repositories even if there are conflicts is so trivial and user friendly even with command line, while ClearCase having tons of GUI tools is a long and laborious process which is also extremely error prone.
All GUI tools require a ton of latency. Even seeing what can be done on a file requires a high speed connection. So right-clicking in the ClearCase tool on a file working from home could take a minute or two having high speed internet because of the extreme amount of networking requirements. Someone can completely mess up the repository or check-ins if they make their view spec different than the team. Which is quite insane that nobody can just check out some branch; they need the appropriate view spec which will incidentally give them the right stuff.
I have absolutely nothing nice to say about CC. I used it for 2 years at 2 companies and dropped it in a heartbeat feeling happy the entire time. It is also impossible to just experiment with at home with your own projects, so you will still learn SVN or Git at home, and be forced to go through ClearCase pains at work. Nobody I know has ever used CC voluntarily. They only use it because some manager at work decided CC is the path to salvation and forced everyone to migrate to it. It was that hated.
ClearCase is not just one thing that makes you say no. It's like living in a house infested with ants. Each ant is just a minor inconvenience at best, but the infestation will drive you mad. I'm trying to consolidate a few comments into an actual post here. I'm not really here to persuade you that one is better than the other, except by way of making a few points:.
ClearCase is a fine tool, but it is a complicated tool. There is no getting around this - it does not have an "easy install" mode. ClearCase "snapshot" views are basically the same thing you would have if you checked out a repository from SVN or CVS - it's a local copy of the source code on your machine, with pointers back into the central server for tools to query version history, etc. You can work with these views without any network connection to the ClearCase server at all once they have been created, and you can "recycle" them to avoid downloading your entire repository again when you want to move to work on another branch, for example.
They appear the same as checking out an SVN repository, but they don't actually copy any files until you make changes.
In this way the view is available immediately, but it obviously cannot be worked with if the main clearcase server is unavailable, and is unpleasant to work with over a high-latency connection.
Also, and this deserves its' own paragraph It's hands down the best merge tool that I've ever used in my life. I firmly believe a lot of bad practice in SCM has developed because of a lack of high-quality merge tools, so CVS users never learned to use branches properly and this fear of branching has propagated to the current day for no particularly good reason.
Ok, all that being said, if you're looking for reasons not to use ClearCase, they're not hard to find, although I think that's the wrong way to go about it. You should come into any SCM situation assuming that ClearCase is too much tool or too complicated a tool for the job, and then see if you have some situation that encourages you to use it anyhow. Having IBM or Rational logos is not a good reason.. In principle, CC is technologically capable, enterprise ready and comparable by features with any modern VCS.
But it has several flaws that make it unusable in any people-oriented environment. For process oriented environments it is probably more appropriate, though I doubt that such environments are appropriate by themselves. Maybe, in military, cosmic or medical software, I don't know. Anyway, I believe that even for these domains there are appropriate and still more friendly tools. In my opinion, their use is limited excepting last one; and they don't compensate flaws.
Dynamic view nice in theory, but not always available in practice. Version tree has much less use in other VCS, while necessary in CC because of proliferation of branches see 6. Triggers, as I know, very detailed and capable, but I think that for most practical tasks SVN hooks are good enough. And now about disadvantages that mostly concerns usability:.
ClearCase seems extremely powerful, from the outside. But really, it's just that the number of commands and options you need to use for basic workflow is so high that these get hidden behind a few aliases or scripts, and you end up with something less powerful than CVS, with the usability of Visual Source Safe.
And any time you want to do something a little more complicated than your scripts allow, you get a sick feeling in your stomach. Compare this with Git, which seems complicated from the outside, but after a week working with it you feel completely in control.
The repository model is simple to understand, and incredibly powerful. Because it's easy to get at the nuts and bolts, it's actually enjoyable to dig below the surface of your daily workflow.
For example, figuring out a trivial task such as how to just view a non-HEAD version of a file in a snapshot view took me a couple of hours and what I ended up with was a complete hack. Not the enjoyable sort of hack either. But in Git, figuring out a seemingly complicated task such as how to interactively commit only some changes, and leave the rest for later was great fun, and all the time I have the feeling that the VCS is allowing me to organise code and history in a way that suits me, rather than history being an accident of how we used the VCS.
At my work, I use Git for all sorts of lightweight tasks, even within ClearCase. When the task's eventually done, I check in to ClearCase, and Git helps me review exactly what I'm changing. Just try to get ClearCase to produce a diff across a couple of files - it can't! Use Google to find out the various hacks people have tried to work around this. This is something version control should do out of the box, and it should be easy! CVS has had this for decades! The support is terrible. We've had tickets open for years.
Our eclipse guru actually fixed a bug in their eclipse plugin locally in about 30 minutes by disassembling the java file. But the ticket still hasn't got past level one support.
Every so often they either try to sneakily close it or ping it back to us 'to try on the latest version' even though we sent them a reproduction recipe which they could try for themselves.
ClearCase is powerful, stable IF properly maintained and supervised but it's slow. Geological sometimes. Dynamic views views lead to horrible build times, snapshot views can take ages to update lunch break for large projects or checkout go home for the day. I'd also suggest avoiding CC where possible. Not counting money, the fact it is such a pain to use that is requires a full time admin is a total joke. The team I was newly assigned to was using a heavyweight tool in an convoluted, error-prone manner.
I first attempted to sell them on my tools and processes of choice. This attempt failed miserably. I was flabbergasted that they would pick such a burdensome environment over one that was both easier and more effective. Turns out that they wanted to be disciplined, and using a painful process felt disciplined to them. It sounds wierd, but it's true. They had a lot of other misconceptions too. After I figured out what they were after, we actually stuck with the same tool suite Serena , but massively changed how it was configured.
My advice to you is to figure out what matters to your team. Ripping on ClearCase won't get you anywhere unless you speak to their interests. Also, find out why they don't want to use alternatives. Basically do a little requirements gathering and fit your tool choices to your needs. Depending on your options, who knows, Clear Case may end up being the best option after all. I'm not totally against ClearCase it does have it's advantages , but to list out the disadvantages:.
The biggest downfall for me is both the performance especially if your VOB is multisite or offsite , and potentially lengthy downtimes. If you're like me and work in a relatively small office as part of a large company with no onsite IT , Clearcase servers going down can cost you the better part of a workday in non-productivity as well as getting the right people to get it fixed. Bottom line, use it only if you really need it for what you are doing and make sure you have a beefy IT budget to maintain it.
ClearCase is perfectly usable if your willing to also use another version control system on top of it! As of the new version of version 7. Personally I would really not want it but apparently some people see that as "an essential feature". Then again During this period we have officially made over integration deliveries and while having up to 6 concurrent development and release efforts.
The network and servers are supported by the IT team. All I can say is we have had virtually no problems coming from the CM side of this huge development effort and were never a show stopper. Our developers where trained with just the basic stuff and a simple steps were given to them whenever a new project branch was created at the request from the project management. Developers should focus on development not SCM or be a tool specialist. The core issue here with finding this a problem is that you have to define if you want to have configuration management performed in your organization which is NOT version management.
Configuration Management is like Project Management: even without a tool you still can do project managment and without a tool you can do Configuration Management. Lots of people have a hard time understanding this and lots of people think Configuration Management is equal to a tool which versions sources of software or something ClearCase is a solution that is build for usage in a Configuration Management environment ERGO: there is a configuration manager just like "there is a project manager".
So what you need to do like in any other software project go back to your requirements and put a list of requirements together on what your organisation wants with configuration management. There lies the key imho on some reactions I read here. ClearCase is not a tool only for end-users entering their sources under version control like subversion or git. I think the choice of a CM system should never lay with developers equal to choosing the right project management tool or the right CRM system.
How to install and configure ClearCase MultiSite…. How to record the uninstallation and how to…. How to record and invoke a response file for…. Installation and configuration of ClearCase with…. Search for " ".
Public, Restricted and Moderated. Sign up or log in Sign up using Google. Sign up using Facebook. Sign up using Email and Password. Post as a guest Name. Email Required, but never shown. The Overflow Blog. Stack Gives Back Safety in numbers: crowdsourcing data on nefarious IP addresses. Featured on Meta. New post summary designs on greatest hits now, everywhere else eventually.
Learn more. Asked 7 years, 2 months ago. Active 3 years, 6 months ago. Viewed 2k times. As said before these licenses were returned to the pool and are being utilized by another machine m2 In the image, i want to remove the highlighted entries.
How can i remove the old license entries from the machine m1? Improve this question. Add a comment. Active Oldest Votes.
An increment block looks like this. Improve this answer.
0コメント