-
Improvement
-
Resolution: Duplicate
-
Minor
Snapshot views are created using switches -stgloc -auto.
Some existing view storage locations may not be valid though - an option to specify which view storage location to use would be handy.
[JENKINS-13234] Option to specify the view storage location - our case 8516
Christian Wolfgang
added a comment - JENKINS-12931 
Iosif Neitzke
added a comment - Has this actually been resolved? If so, I can not easily find an option to control it.
Iosif Neitzke
added a comment - Has this actually been resolved? If so, I can not easily find an option to control it. 
Jens Brejner
added a comment - Hi Iosif.
I do not think this has been implemented. Do you agree that we are talking about which view-server storage location should be used, and not about where in the local filesystem, the snapshot view will be created ?
Jens Brejner
added a comment - Hi Iosif.
I do not think this has been implemented. Do you agree that we are talking about which view-server storage location should be used, and not about where in the local filesystem, the snapshot view will be created ? Iosif Neitzke
added a comment - Yes, I agree that we are talking about view-server storage location. So far we have always been fine with "view" in the workspace for the snapshot view, but sometimes control over the view-server storage would be time-saving, as ClearCase servers and our network are difficult. We would be thrilled if there was simply an option where the view-server storage was always located with the view, or configurable to a hard-coded directory with default naming patterns on a per-node basis. Thanks.
Iosif Neitzke
added a comment - Yes, I agree that we are talking about view-server storage location. So far we have always been fine with "view" in the workspace for the snapshot view, but sometimes control over the view-server storage would be time-saving, as ClearCase servers and our network are difficult. We would be thrilled if there was simply an option where the view-server storage was always located with the view, or configurable to a hard-coded directory with default naming patterns on a per-node basis. Thanks. Jens Brejner
added a comment - Do you allow clients to be view-servers ? Personally I think that is very inconvenient seen from a ClearCase administrative point of view - but is an absolutely valid use. But I am still a bit confused, would you like to be able to control (change) the folder name 'view' which we create in the workspace root, or do you need to be able to use a different UNC path, as opposed to the one ClearCase gives you with cleartool mkview option -stgloc -auto ?
Jens Brejner
added a comment - Do you allow clients to be view-servers ? Personally I think that is very inconvenient seen from a ClearCase administrative point of view - but is an absolutely valid use. But I am still a bit confused, would you like to be able to control (change) the folder name 'view' which we create in the workspace root, or do you need to be able to use a different UNC path, as opposed to the one ClearCase gives you with cleartool mkview option -stgloc -auto ?
Iosif Neitzke
added a comment - To clarify, we only need an option that would let us use "cleartool mkview -vws view-storage-pname ..." where we could configure "view-storage-pname" to be something like ${CURRENT_JENKINS_NODE}/${VIEW_STORAGE}/${JOB_NAME}.
Iosif Neitzke
added a comment - To clarify, we only need an option that would let us use "cleartool mkview -vws view-storage-pname ..." where we could configure "view-storage-pname" to be something like ${CURRENT_JENKINS_NODE}/${VIEW_STORAGE}/${JOB_NAME}. Jens Brejner
added a comment - Ok, now I think I understand, I will get back to you. Jens Brejner
added a comment - Hi Iosif.
The original idea behind this case was to offer the ability to specify a name which is different from view. This would be implemented as a global configuration option for snapshot view folder name. Today the option is not available, any view CCUCM creates are located in the a job's workspace as ${workspace}\view\ As said, we can make a global configuration option with default value 'view', but whichever string is in the global configuration, will be used by all CCUCM jobs.
Your need is a bit different and as I understand it, it has nothing to do with the use of string 'view' for the local data representation. You need an option, where we change our use of the mkview command so we use -vws <UNC-path> instead of -stgloc -auto.
Do you see this as a global configuration option or as a per job option ? From my point of view I think we should arrange an online meeting and talk this through.
Jens Brejner
added a comment - Hi Iosif.
The original idea behind this case was to offer the ability to specify a name which is different from view. This would be implemented as a global configuration option for snapshot view folder name. Today the option is not available, any view CCUCM creates are located in the a job's workspace as ${workspace}\view\ As said, we can make a global configuration option with default value 'view', but whichever string is in the global configuration, will be used by all CCUCM jobs.
Your need is a bit different and as I understand it, it has nothing to do with the use of string 'view' for the local data representation. You need an option, where we change our use of the mkview command so we use -vws <UNC-path> instead of -stgloc -auto.
Do you see this as a global configuration option or as a per job option ? From my point of view I think we should arrange an online meeting and talk this through.
pseudo linking