Currently it is not possible to “disable” any tasks. We assume that if you have access to modify the config file, then you can call any task.
The only way I could think of doing it, would be to get the code for CC.NET, delete the task from there and compile (and deploy) a custom version of CC.NET. Craig From: [email protected] [mailto:[email protected]] On Behalf Of Ruben Willems Sent: Thursday, 18 June 2009 10:42 p.m. To: [email protected] Subject: [ccnet-user] Re: Can I disable some Task Blocks Hi ok, got the picture, but what is stopping the malicious one of doing the 'build publish' inside the buildscript? --> nant has a copy task --> you can call a batch file --> ... so you fix 1 hole, but there are dozens others left if you want to make sure that the code stays on the source control server I would use configure the os that way. no mapped drives, no possible connection to the internet, ... This should be possible with the useraccount you use for the ccnet service just give it acces to your source control server, but no other. with kind regards Ruben Willems 2009/6/18 Cao Shu <[email protected]> Hi, I want to make sure <buildpublisher> won't work on my CC.Net server for some security reasons. I'm in charge of the server, but some one else is in charge of the ccnet.config. What I really want is that people can use it to compile the code, but can not copy the code out. So I want to disable the <buildpublisher>, and write a customized scripts that can be used in <exec> tasks to do the publishing which will refuse to copy the .c/.cpp files. Thanks On 6月18日, 下午6时21分, Ruben Willems <[email protected]> wrote: > Hi > > I do not understand really > if you do not want to use the build publiser, > just remove it from the config. > > Can you elaborate a bit more on the situation? > > with kind regards > Ruben Willems > > > > On Thu, Jun 18, 2009 at 12:18 PM, Cao Shu <[email protected]> wrote: > > > Hi, > > > Can I disable some Task Blocks? For example, I want to disable the > > use of "Build Publisher". If the blocks is defined in the config file, > > either reporting error or ignoring it are both ok for me. > > > Thanks.
