wipe out workspace

[Irfan Sayed]

hi all,

is there any way, restrict the user from wiping out the workspace.
there is a option called "wipe out workspace" i don't want normal user to delete workspace. only administrator should delete the workspace
plz suggest

regards,
irfan

[Irfan Sayed]

but what i need is , every normal user should not be able to delete/wipe the workspace of a project which he has access

plz suggest

On Thu, Jun 16, 2011 at 6:22 PM, Robert Simon <robert...@avid.com> wrote:

Hi Irfan,

 

Maybe you need to make a job which only can be called by admin and this uses https://wiki.jenkins-ci.org/display/JENKINS/Workspace+Cleanup+Plugin

 

Regards,

Robert

 

From: jenkins...@googlegroups.com [mailto:jenkins...@googlegroups.com] On Behalf Of Irfan Sayed
Sent: Donnerstag, 16. Juni 2011 12:59

To: jenkin...@googlegroups.com; jenkins...@googlegroups.com
Subject: wipe out workspace

[Irfan Sayed]

i found that if i select/click the "build" and "workspace" option in the permission group in the project configuration page ,  then user can see "wipe out workspace"
but if i uncheck the "build" then user can see just "workspace" and he does not have option to wipe out the workspace.
but issue is, user looses the ability to build the project

i need something like : user shud be able to build the project , but shud not able to wipe the workspace
plz suggest

[Irfan Sayed]

thanks. so , is there any option to do these/?
if not, how can i file enhancement request ??

regards
irfan
 

On Thu, Jun 16, 2011 at 9:07 PM, K96 <koo...@gmail.com> wrote:

Another relating request from me K96.

I want 'clear workspace' option, such as:
 * 'wiping out workspace' : /bin/rm -rf  <workspace>
 * 'clear workspace' :  /bin/rm  -rf <workspace>/*

It's because deleting workspace folder itself would often cause
serious problems
in such cases as I mentioned in the previous post.
But I suppose there are more cases where deleting only child-trees
under workspace  is not so harmful.

Regards,
Kuh96

On Jun 17, 12:17 am, K96 <koo...@gmail.com> wrote:
> Hi,  Les Mikesell  and irfan
>
> I agree with both of you. IMHO:
>
> (1) Les Mikesell is right.
> Wipe out workspace anytime and start build, but this build will never
> fail.
> This "clean and full build" is very important principle for build
> reproductivity.
> But this is an ideal case.
>
> (2) irfan is also right.
> It's because some/many/most of Jenkins  users  seems to be not so
> skillful.
> They often write such bad jobs depending on existing contents in the
> workspace,
> but they love Jenkins and Jenkins is very useful CI tool even for
> them.
>
> In addition, there are some cases when such bad jobs are needed,
> for example,  when using IDE  for build such as eclipse, visual studio
> or some other tools which require dirty folder/file configuration.
>
> So I would agree with irfan, rather than  Les Mikesell.
> It's because it is a problem of users, not Jenkins.
> Jenkins should accept even such users.
>  I think that wiping workspace should be permitted only to
> job creators by default, for example.
>
> Regards,
> Kuh96
>
> On Jun 16, 11:40 pm, Les Mikesell <lesmikes...@gmail.com> wrote:

>
> > On 6/16/2011 8:17 AM, Irfan Sayed wrote:
>
> > > i found that if i select/click the "build" and "workspace" option in the
> > > permission group in the project configuration page ,  then user can see
> > > "wipe out workspace"
> > > but if i uncheck the "build" then user can see just "workspace" and he
> > > does not have option to wipe out the workspace.
> > > but issue is, user looses the ability to build the project
>
> > > i need something like : user shud be able to build the project , but
> > > shud not able to wipe the workspace
> > > plz suggest
>

> > I'm curious as to why this is important.  Normally you would treat
> > workspaces as disposable and reproducible from your source control
> > system and the job definition so it can be run on any slave and just
> > copy out the build results if you want to keep them.
>
> > --
> >    Les Mikesell
> >     lesmikes...@gmail.com

[Irfan Sayed]

can someone please give me pointer ??

--irfan

[Romain]

FYI I've just committed a change which adds a new WipeOut permission when the hudson.security.WipeOutPermission system property is set to true. Cf. https://wiki.jenkins-ci.org/display/JENKINS/Features+controlled+by+system+properties.

RS