Hoping someone might have some insight here. I have a small shell titled xrunner.sh.
#!/bin/bash
ct checkout -nc parentFolder
cd parentFolder/
ct mkdir -nc directory
ct checkin -nc directory
cd ..
ct checkin -nc parentFolder
pwd
When the commands are run individually on the CLI they all work fine, When run from the bash however the following is thrown back at me:
ct: bad phone number -- parentFolder
ct: bad phone number -- -nc
ct: bad phone number -- checkout
: No such file or directory
ct: bad phone number -- directory
ct: bad phone number -- -nc
ct: bad phone number -- mkdir
ct: bad phone number -- directory
ct: bad phone number -- -nc
ct: bad phone number -- checkin
: No such file or directory
ct: bad phone number -- parentFolder
ct: bad phone number -- -nc
ct: bad phone number -- checkin
Would anyone happen to know why this is or point me to some web reference that explains this? Thanks in advanced.
The problem you get with
ct: bad phone number...
is because there is actually another binary calledct
. You can runtype -p ct
in bash to find which (too many years since I had the same problem so I do not remember where it was (/usr/xpg4/bin ??)).So as VonC suggest, make an alias for ct.
That means you don't have defined the alias 'ct' properly
add:
Note: if you want to add a directory to source control, don't forget to call mkelem
See "Command line add to Source control of a directory with files in a dynamic view returns Error".
Notes:
ct setview
won't allow furtherct
commands to work, becausesetview
spawns a sub-shell. See for instance "Python and ClearCasesetview
" for more onsetview
.So
ct
will work, except if you have furtherct
commands in a script after act setview
./usr/bin/ct
command