| Summary: | Request shell access | ||
|---|---|---|---|
| Product: | Community | Reporter: | Maxime Porhel <maxime.porhel> |
| Component: | CommitterTools | Assignee: | Eclipse Webmaster <webmaster> |
| Status: | RESOLVED WONTFIX | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | denis.roy, mikael.barbero, pierre-charles.david |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Mac OS X | ||
| Whiteboard: | |||
|
Description
Maxime Porhel
As you have a HIPP with appropriate permissions to write to the download area, why don't you use it to publish builds of Sirius? I am a bit picky, but this is only to understand what is preventing you from using your HIPP. I will grant you shell access if you confirm you still need it. (In reply to Mikael Barbero from comment #1) > I am a bit picky, but this is only to understand what is preventing you from > using your HIPP. I will grant you shell access if you confirm you still need > it. Our HIPP only published nightlies. The request is for Maxime to be able to promote specific nightlies as Stable or Milestone build, as per https://wiki.eclipse.org/Sirius/Releng, when both Laurent and I (who usually do it) are unavailable (which will happen this summer). As Mikael has suggested, we're a bit picky with shell access. Could those promotion steps not be contained within Hudson jobs? You were not that picky last year in giving shell access to Laurent Redor https://bugs.eclipse.org/bugs/show_bug.cgi?id=417187#c1 :) But I completely understand the concerns (and agree with them). I'll have a look at how much work a promotion job would require. Closing as 'wontfix' as using HIPP job to do the deployment is now our recommended practice. -M. |