Good point Peter.  I've used that in the past too.  I wonder though, and I 
don't have a ClearCase system up and running at my current job, are you 
still able to use all of the Cleartool commands in the View extended 
context?  I can't remember and if you cannot, that'd be something good to 
note that limitation.  Are there any other limitations with derived 
objects, config records etc?


On Monday, August 26, 2013 10:05:09 AM UTC-4, [email protected] wrote:
>
> Hi,
>  
> The easiest way ist to use "View extended pathnames" instead of doing a 
> 'setview'.
> i.e.
>  
> cleartool startview <viewname>    # Just to make sure that the View is 
> started on this host.
> cd /view/<viewname>/vobs/....
> ..
> ...
>  
> As long as You do not execute any commands that are using absolute paths 
> to /vobs/... but instead relative paths,
> this works perfectly.
>  
> /Peter
>  
>  
>
> Den fredagen den 23:e augusti 2013 kl. 14:23:34 UTC+2 skrev Shannon Kerr:
>
>> Jeff is absolutely right of course.  The default mode for "ct setview" is 
>> to spawn a new shell.  The only way to use this within Jenkins is to use 
>> the -exec option.
>>
>> We had a similar situation several years ago.  We would actually generate 
>> a script on the fly to do what we needed to do for that particular build 
>> and then we'd execute "ct setview -exec <script> <view>" to run the script 
>> within the desired CC View.  The reason we gen'd the script on the fly was 
>> so that we could support several different build types for several 
>> different teams AND so we could steps in different Views in parallel.
>>
>>
>> On Wednesday, August 21, 2013 7:49:10 AM UTC-4, M Polański wrote:
>>>
>>> Executing 
>>> [quote]cleartool setview someexistingview[/quote] 
>>> in an execute shell action on a Jenkins instance running on a redhat 
>>> server 
>>> I get the following in the console output: 
>>> [quote]stty: standard input: Invalid argument[/quote]. 
>>> Other cleartool commands like "lsview" or "pwv" are working fine. 
>>>
>>>
>>>
>>> -- 
>>> View this message in context: 
>>> http://jenkins-ci.361315.n4.nabble.com/ClearTool-on-shell-tp4676820.html 
>>> Sent from the Jenkins users mailing list archive at Nabble.com. 
>>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to