Re: [p4] how to protect job in perforce

I have an idea/theory about this. It's untested and I have no idea if it  
will work. Maybe someone has the gumption.
Do a 'p4 undoc' and read up on the 'spec' type of depot. Spec depots keep  
historical artifacts in regard to metadata, including jobs. Maybe (maybe)  
a trigger could be written that monitors changes in the jobs section, then  
reverts any changes not made by a superuser?
Now that I'm thinking about it, there really are no checkins per se to  
this depot, so it would have to be some sort of daemon.
Of course, this might not work at all. Spec depots ignore protections  
(wouldn't that be nice if they didn't?) so I don't know how this would  
react to a command such as 'obliterate'.
-Matt


On Tue, 19 Oct 2004 16:44:01 +0100, Paul Goffin  
<Paul.Goffin@xxxxxxxxxxxxxx> wrote:
> No, perforce jobs isn't subject to any access control.
> The only way to achieve some elements of this is to use something like
> the P4DTI integration to bugzilla.
> Then bugzilla will overwrite any jobs that are changed by someone who
> has no rights to make the change.
> Even if you use this integration you can't prevent any perforce user
> viewing jobs you'd prefer they didn't have access to.
> Paul.
> -----Original Message-----
> From: Azoulay, Zacky [mailto:zacky.azoulay@xxxxxxx]
> Sent: 19 October 2004 16:20
> To: 'perforce-user@xxxxxxxxxxxx'
> Subject: [p4] how to protect job in perforce
>
>
>
> Hi,
>
> I want to create perforce job for each feature. However any developer
> can delete those jobs.
>
> Is there any way to disable delete jobs in perforce (like a change list
> after submiting).
>
> Is there any way to enable only super user to delete jobs in perforce.
>
> Regards zacky
>
>
>
> **********************************************************************
> This email and any files transmitted with it are confidential and
> intended solely for the use of the individual or entity to whom they
> are addressed. If you have received this email in error please notify
> the system manager.
>
> This footnote also confirms that this email message has been swept for
> the presence of computer viruses.
> ************************************************************************
> *****
_______________________________________________
perforce-user mailing list  -  perforce-user@xxxxxxxxxxxx
http://maillist.perforce.com/mailman/listinfo/perforce-user