I was doing a checkout of a file in ClearCase, and I was unable to checkout this file from the frozen view because of this file which was a bleed-thru file. I thawed the view, and then I was able to check out the file, so I really do not have a problem at this time.
I do have a question, though. What is a bleed-thru file in ClearCase? Any ideas? I have not heard this term before, and was interested, partly because it just sounds so cool!
Not sure what you call a "frozen view", except if you are referring to a snapshot view.
A "bleed-through" file (again, I am not familiar with the 'bleed-thru' spelling) could be related to multi-site views, where:
This navigator is called a "bleed through" view because it lists both local files/members and remote objects, files and members.
However, if a file or member exists both locally and remotely, it is not shown twice.
Rather, it is only shown once, and its icon and bracketed text identify it as existing in both places.
If you have any screen captures of that term used in ClearCase, I am interested;)
Related
I moved a file one folder up. Now in Azure DevOps in commit content I see [rename] written next to the file, but I do not see how the file name was changed (i.e. I do not see the old file name). Is there any way I could find this out?
Hovering over the file name in the commit content diff explorer shows a title containing the information I was looking for. It says {new branch name} [rename] renamed from {old branch name}.
Would be nice not to have to hover over to see this though. Since sometimes there are a lot of files. Hopefully Microsoft will add another way to view this in future.
So the joyful sys admins like to lock down the vob between 9p-7a for backups... why, one can only speculate and loose hours of productivity.... oh wait that is happening anyways since the vob is locked for ... 10 hrs... anyways I digress.
So I recently started using dynamic views and have been pleasantly surprised at how useful it has been with constant integration. But with my old snapshot views when the vob was locked I could always hijack a file and convert it to a check out later, but that is not allowed in a dynamic view so following the following post:
ClearCase: Can I hijack a file in dynamic view?
I've managed to 'hijack' or eclipse said files to continue working, but now comes the question... what is the easiest way to convert said eclipsed files to checkouts?
In a snapshot view with a hijack you simply pass the '-usehijack' flag to the co command, but how do you do this with a eclipsed file.
I can remove the file and get the original version back, but then I'd lose my changes.
The only way I can think of is to move the file elsewhere, let clearcase replace the file, then checkout and copy the file back, but is that the only way?
Thanks to all in advance.
You need to:
rename the file
checkout the original file (no longer eclipsed)
overwrite the checked out file with your copy.
A bit cumbersome, but scriptable.
It's been a little while, and I don't have ClearCase access anymore, but I think that a 'cleartool co -nodata' might do the trick for you.
For reasons unknown, a folder was checked out to me in ClearCase. A coworker was working on a word document stored in that folder. I undid the checkout on the top level folder. Her document disappeared and she doesn't have a local copy. Have I totally screwed her over here? Is there any way we can get it back? Is it stored somewhere on the server and we just can't see it with the standard GUI interface? I was under the impression that you couldn't add to a folder if someone had it checked out.
If it is a dynamic view, the only place it can still be is in the view storage.
But, dynamic or snapshot, first check the \yourVob\lost+found folder: it is for any files:
added to source control
with no parent folder referencing it (which is exactly what you have done by undo-checkouting said parent folder of the work document).
See "About the lost+found directory" for more on that special folder.
If you find it there (with an "extended name"), then see "To move an element from the lost+found directory" in order to restore the file.
I'm thinking of Mask as in a circuit Mask (I think)- let me explain with a handy chart
The common source would be physically in c:\source
Instance A would be physically in c:\instanceA but initially have nothing but symlinks to everything in c:\source
Instance B would be physically in c:\instanceB but initially have nothing but symlinks to everything in c:\source
As you made changes to Instance A and Instance B, you would have create a mask that would hide files from CommonSource if they were deleted from the Instance folders and create a new physical file in the instance directory if an existing Common Source file was modified.
New files would live in the instance folders but never make it back to the Common Source.
This type of setup would be very useful for a project where I want to do many different types of small tweaks to multiple instances where distinct threads would work on distinct instances.
I know about symbolic links but they fall short in the case of modifying a file.
Is there anything that can accomplish this? If not, should I try to make this and patent it? Seems like a good idea to me.
I would be on Windows Server 2008 or later.
Fearing I'm stating the obvious, but git is one tool that can be used to achieve this behavior.
Make your "Common Source" a git repository
Clone the repository twice to "InstanceA" and "InstanceB"
In each instance, check out a new, unique branch
As changes are made in "Common Source" you can merge those changes into "InstanceA" and "InstanceB" while maintaining the "MASK" (changes to the branch) you've created for each.
This has the added benefit of allowing changes from "Common Source" to be pulled as you wish instead of having changes to "Common Source" pushed out to each instance (something I imagine would be less desirable and more prone to error).
You're looking for a union mount. Unfortunately, I'm not aware of any implementations for Windows, but there are several available for Linux, notably UnionFS.
In general they are used for making a read-only filesystem look like it's read-write: typically on live-CDs.
Since Windows 7 you can use libraries, which will allow you to include files from more than one physical location.
Windows 7 also include VirtualStore type of folder (for example, when creating or modifying a file in Program Files folder, it will actually be created in a user specific folder:
C:\Users\user\AppData\Local\VirtualStore. However - I don't know how you can create this type of folders yourself, and also, as far as I know, you can add and modify files, but not delete files in that way.
You'll want a versioning control system that supports per file checkout and permissions. Then you just need to set up a simple API converter that takes file-system commands and converts them to versioning control commands.
Delete -> disable permission to access file.
Directory commands should look for local copies and things you have permission to access.
Open -> grab local copy, on fail check-out file from repository.
Save -> disable permission, save local copy. //Avoid duplicates being seen.
Close without saving -> if permission to access from repository, delete local copy.
((By the way, this storage optimization seems somewhat spurious for versioning. Disk space is relatively cheap.
If your interest isn't in versioning, I'd suggest looking into separating out the information you would potentially want as volatile and creating configuration files for each branch. This, of course, requires a predictable pattern to the changes.))
IBM Rational ClearCase is version control system which does file-mask-like behaviour. It is known as MVFS: MultiVersion File System and can be mount to a workstation like a ordinary network drive.
ClearCase server (aka. VOB) you can store several versions of the same file, each on different code branch. The sets of files visible by user are called views. Each view has a configuration (aka. configuration specification), which defines what files and versions are visible for current user. Typical file looks like this:
# From wikipedia: http://en.wikipedia.org/wiki/IBM_Rational_ClearCase#Configuration_specifications
# Show all elements that are checked out to this view, regardless any other rules.
element * CHECKEDOUT
# For all files named 'somefile', regardless of location, always show the latest version
# on the main branch.
element .../somefile /main/LATEST
# Use a specific version of a specific file. Note: This rule must appear before
# the next rule to have any effect!
element /vobs/project1/module1/a_header.h /main/proj_dev_branch/my_dev_branch1/14
# For other files in the 'project1/module1' directory, show versions
# labeled 'PROJ1_MOD2_LABEL_1'. Furthermore, don't allow any checkouts in this path.
element /vobs/project1/module1/... PROJ1_MOD2_LABEL_1 -nocheckout
# Show the 'ANOTHER_LABEL' version of all elements under the 'project1/module2' path.
# If an element is checked out, then branch that element from the currently
# visible version, and add it to the 'module2_dev_branch' branch.
element /vobs/project1/module2/... ANOTHER_LABEL -mkbranch module2_dev_branch
is TYPO3 doing some indexing of the filesystem into database?
We try to add a video to our page here, but video isn't selecable from the file window altough its put into the right directory.
The Fileadmin says "9 records found" in the folder and is displaying only 7 Files, because someone might have deleted two of the files out of the folder.
But the new video file we've put there won't be displayed, too.
Is there any way to manually start TYPO3s file indexer?
I don't think TYPO3 does any indexing of the files; it just reads the list of the files straight off the filesystem. So there's no file indexer to start.
My suggestion for your problem would be to check the permissions on the file you uploaded and make sure it's readable by whatever user the Web server is running as ('apache', 'www-data', etc). If it isn't readable by the Web server it won't show up in the fileadmin area.
Okay guys, I feel stupid right now - altough I can't really explain the behavior...
What happened seemes to be some strange caching failure.
If you click on the "choose file" button it shows the window as seen in the screenshot above, displaying the last used folder.
But: this view is somehow cached.
If you select the same folder again from the file tree from the left, the view is updated and the missing files are shown -.-