Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 311761 - Misnamed Virgo job
Summary: Misnamed Virgo job
Status: CLOSED FIXED
Alias: None
Product: Community
Classification: Eclipse Foundation
Component: CI-Jenkins (show other bugs)
Version: unspecified   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: CI Admin Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-05-05 12:11 EDT by Steve Powell CLA
Modified: 2010-05-06 11:21 EDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Steve Powell CLA 2010-05-05 12:11:48 EDT 
Job created for Virgo builds called:
 virg.web-server.snapshot
should be called:
 virgo.web-server.snapshot

Please re-name. Thank you.
Comment 1 David Carver CLA 2010-05-05 12:34:17 EDT 
(In reply to comment #0)
> Job created for Virgo builds called:
>  virg.web-server.snapshot
> should be called:
>  virgo.web-server.snapshot
> 
> Please re-name. Thank you.

You should have rename rights yourself for the job.
Comment 2 Steve Powell CLA 2010-05-06 05:02:27 EDT 
(In reply to comment #1)
> (In reply to comment #0)
> > Job created for Virgo builds called:
> >  virg.web-server.snapshot
> > should be called:
> >  virgo.web-server.snapshot
> > 
> > Please re-name. Thank you.
> 
> You should have rename rights yourself for the job.

It would be nice to have rename rights - but when I try it it says I need create permission -- which I don't have.

Please rename.
Comment 3 Steve Powell CLA 2010-05-06 05:04:52 EDT 
(In reply to comment #1)
> (In reply to comment #0)
> > Job created for Virgo builds called:
> >  virg.web-server.snapshot
> > should be called:
> >  virgo.web-server.snapshot
> > 
> > Please re-name. Thank you.
> 
> You should have rename rights yourself for the job.

Is this a bug?  I'll raise another one then -- or perhaps this bug can act that way.
Comment 4 David Carver CLA 2010-05-06 09:08:06 EDT 
Alright it's renamed.
Comment 5 Steve Powell CLA 2010-05-06 10:10:02 EDT 
Thank you -- but were you right to say I should have been able to do it myself?
Comment 6 David Carver CLA 2010-05-06 10:15:54 EDT 
(In reply to comment #5)
> Thank you -- but were you right to say I should have been able to do it myself?

It looks like unless we give you Delete access, on the project, you can't rename it.
Comment 7 Steve Powell CLA 2010-05-06 11:21:46 EDT 
(In reply to comment #6)
> (In reply to comment #5)
> > Thank you -- but were you right to say I should have been able to do it myself?
> 
> It looks like unless we give you Delete access, on the project, you can't
> rename it.

The response I got implied that create access was what I lacked. Delete permission is in the permissions matrix in the job. I guess I need both. 

This is due to the >implementation< of rename.  

It would be better to allow renames as part of the modification permissions, and implement it as a (controlled) create(clone)/delete, which were not subject to permissions control.

I'll raise this as an enhancement request.