How can I use ClearCase to “add to source control …” recursively?

by

I would rather go with the clearfsimport script, better equipped to import multiple times the same set of files, and automatically:

  • add new files,
  • make new version of existing files previously imported (but modified in the source set of files re-imported)
  • remove files already imported but no longer present in the source set of files.
  • make a clear log of all operations made during the import process.

So if your ‘zip-file delivery needs to be updated on a regularly basis, clearfsimport is the way to go, but with the following options:

clearfsimport -preview -rec -nset c:\sourceDir\* m:\MyView\MyVob\MyDestinationDirectory

Note the :

  • -preview option: it will allow to check what would happen without actually doing anything.
  • ‘*’ used only in Windows environment, in order to import the content of a directory
  • -nset option.

From CMWiki, about that ‘nset’ option:

By default, clearfsimport is meant to be used by the vob owner or a privileged user, but users often overlook the -nsetevent option, with which it may be used by any user.
This option drives clearfsimport not to set the time stamps of elements to this of the source file object outside the vob (which requires privileged access).
There is a minor non-obvious side-effect with this: once a version will have been created with a current time stamp, even the vob owner will not be able to import on top of it a version with an older (as it would be) time stamp, without this -nsetevent option. I.e. once you use this option, normal or privileged user, you are more or less bound to use it in the continuation.

More Related Contents:

  1. ClearCase advantages/disadvantages [closed]
  2. How do I perform a recursive checkout using ClearCase?
  3. When should you branch?
  4. Why is a 3-way merge advantageous over a 2-way merge?
  5. Using IPython / Jupyter Notebooks Under Version Control
  6. Should I store generated code in source control
  7. What is the cleverest use of source repository that you have ever seen?
  8. IntelliJ IDEA 9/10, what folders to check into (or not check into) source control?
  9. Source control vs. Revision Control?
  10. What’s the best three-way merge tool? [closed]
  11. Storing third-party libraries in source control
  12. Named Branches vs Multiple Repositories
  13. Mercurial — revert back to old version and continue from there
  14. Flexible vs static branching (Git vs Clearcase/Accurev)
  15. Mercurial Subrepos – How do you create them and how do they work?
  16. How to edit incorrect commit message in Mercurial? [duplicate]
  17. What’s the easiest way to commit and push a single file while leaving other modifications alone?
  18. Source Control – Distributed Systems vs. Non Distributed – What’s the difference?
  19. Is there a way to keep Hudson / Jenkins configuration files in source control?
  20. Branching Strategies [closed]
  21. Comparison between Centralized and Distributed Version Control Systems [closed]
  22. Can you “ignore” a file in Perforce?
  23. Mercurial: Merging one file between branches in one repo
  24. What is the difference between hg forget and hg remove?
  25. How often to commit changes to source control? [closed]
  26. Do you continue development in a branch or in the trunk? [closed]
  27. TFS 2017 – how build/deliver only changed files?
  28. How to find untracked files in a Perforce tree? (analogue of svn status)
  29. Code version change “rules” [closed]
  30. What is the difference between all the different types of version control?

Leave a Comment