Our triggers all have a
-execwin "cmd /C trigger-script.pl"
this assumes that .pl is associated with perl and perl is in the path.
We also have a set of triggers that are perl wrapped into a .bat file. That
saves the cmd /C.
You still need perl in your path, but don't have to have the .pl
association. (you can extend the path in the .bat, and have not to worry
about it)
In the long run you will have to not use drive names, unless you expect all
your users to have exactly the same drive letters assigned.
Also in the long run you probably won't be happy with ccperl. Get the active
state perl and install it on a central share and use it from there (via unc
path name).
Martina
Don't Postpone Joy - Have Fun
Martina Riedel Siemens Enterprise Networks, Inc.
phone: 561-923-1774 Martina.Riedel@ICN.Siemens.com
-----Original Message-----
From: Girba, Nicoleta [mailto:NICOLETA_GIRBA@SRTelecom.com
Sent: Wednesday, July 11, 2001 5:50 PM
To: cciug (E-mail)
Subject: RE: [cciug] Trigger unable to run
Thank you for your quick answers!
Yes, I'm using NT. I've changed the trigger creation command as you
suggested and no error messages are shown but...the trigger do nothing when
tested on the directory to which I applied the trigger.
Y:\SCM_Vob\adlib>cleartool mktrtype -element -preop checkin -nc -execwin
"D:\ProgramFiles\Rational\ClearCase\bin/ccperl.exe
Y:SCM_Vob\trigs\metrics_resv.pl" my_trigco
I'll try to change the perl script and test again.
Thank you,
Nicoleta
> -----Original Message-----
> From: chunbo shao [SMTP:chunbo.shao@sabre.com
> Sent: Wednesday, July 11, 2001 4:57 PM
> To: Girba, Nicoleta
> Subject: Re: [cciug] Trigger unable to run
>
> hi, Nicoleta
>
> 2 things here.
> if you run your trigger on unix, pls give path to your perl as 1st line in
> your
> perl script, ex, #!/packages/bin/perl.
>
> 2nd, if you run your trigger on NT, pls give ccperl in your -exec, ex,
> ....-exec 'ccperl Y:\SCM_Vob\trigs\metrics_resv.pl' trigname
>
>
> good luck
>
>
> Chunbo
>
>
>
> "Girba, Nicoleta" wrote:
>
> > Hello group,
> >
> > I know there is something that I'm missing in the creation of my
> > trigger...but I cannot identify the problem.
> > I've defined an element trigger type and then attach the trigger to a
> > directory element (these trials are part of "my triggers learning curve"
> ).
> >
> > Please see below the creation of the trigger 'my_trigco' .
> >
> > Y:\SCM_Vob>cleartool mktrtype -element -preop checkin -nc -exec
> > 'Y:\SCM_Vob\trigs\metrics_resv.pl' my_trigco
> > Created trigger type "my_trigco".
> >
> > Y:\SCM_Vob>cleartool mktrigger my_trigco adlib
> > Added trigger "my_trigco" to inheritance list of "adlib".
> > Added trigger "my_trigco" to attached list of "adlib".
> >
> > The perl script is a very simple one (in metrics_resv.pl ):
> > if ($CLEARCASE_RESERVED = 1)
> > {
> > exit(0);
> > }
> > else
> > {
> > exit(1);
> > }
> >
> > I was performing the following actions in order to test the trigger:
> > * the "adlib" directory checkedout unreserved;
> > * added a new file into "adlib" directory;
> > * checkin "adlib" directory.
> >
> > The result is an error message:
> > Can't exec "Y:\SCM_Vob\trigs\metrics_resv.pl":|@
> > Trigger action "-exec 'Y:\SCM_Vob\trigs\metrics_resv.pl'" unable to run:
> > Exec format error.
> >
> > Could you please help with a suggetion?
> >
> > Thank you,
> >
> > Nicoleta
> >
> > - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
> >
> >
> >
> > http://clearcase.rational.com/cciug/mailing_list.html
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
This archive was generated by hypermail 2b29 : Tue Jul 31 2001 - 22:03:54 EDT