| Summary: | Misnamed Virgo job | ||
|---|---|---|---|
| Product: | Community | Reporter: | Steve Powell <zteve.powell> |
| Component: | CI-Jenkins | Assignee: | CI Admin Inbox <ci.admin-inbox> |
| Status: | CLOSED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | d_a_carver |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
|
Description
Steve Powell
(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. (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. (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. Alright it's renamed. Thank you -- but were you right to say I should have been able to do it myself? (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. (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. |