Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-5389

Allow an option to disable cleartool mount -all

    • Icon: Improvement Improvement
    • Resolution: Fixed
    • Icon: Major Major
    • clearcase-plugin
    • None
    • GFv3, Linux

      I notice the newest version of the ClearCase plug-in automatically mounts all the VOBs. This is the safest way to make sure the VOB is mounted when looking for changes but it could lead to errors specially in *nix land. If all the VOBs are mounted, lets say half of the VOBs are located on server A and the other half are located on server B, and one of the VOB servers, server B, goes down it will cause every server that mounted the VOBs located on server B in NFS land to not respond (stale NFS handle) because it was mounted on either the master/slave node. If the project only loads 2 VOBs, the SCM polling shouldn't mount every VOB (50 VOBs) but only the 2 required VOBs. In most cases, the ClearCase administrator has a startup script to mount all the VOBs or a specific set of VOBs. I think the cleartool mount -all should be optional or the plug-in should mount the VOBs that are in the load rules only.

          [JENKINS-5389] Allow an option to disable cleartool mount -all

          corona4456 added a comment -

          I'm running into this problem as well on the Linux side. I don't care of which fix is made as long as it's an optional configuration (probably per job).

          corona4456 added a comment - I'm running into this problem as well on the Linux side. I don't care of which fix is made as long as it's an optional configuration (probably per job).

          Garen Parham added a comment -

          In other systems I've built, I parsed out the VOBs to be mounted from the config-spec load rules or the CRs from previously successful DOs.

          Garen Parham added a comment - In other systems I've built, I parsed out the VOBs to be mounted from the config-spec load rules or the CRs from previously successful DOs.

          Fixed a long time ago (mount -all has been removed, it should be handled separately)

          Vincent Latombe added a comment - Fixed a long time ago (mount -all has been removed, it should be handled separately)

            abayer Andrew Bayer
            mezlight mezlight
            Votes:
            6 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: