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
Hi,
The easiest way ist to use "View extended pathnames" instead of doing a
'setview'.
i.e.
cleartool startview # Just to make sure that the View is
started on this host.
cd /view//vobs/
..
...
As long as You do not execute any commands that are using absolute paths to
/vobs/... bu
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
users@googlegroups.com
Subject: EXTERNAL: ClearTool on shell
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 c
ot; 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&qu
