You are viewing a plain text version of this content. The canonical link for it is here.
Posted to infrastructure-issues@apache.org by "Gavin (JIRA)" <ji...@apache.org> on 2013/08/06 14:30:49 UTC

[jira] [Closed] (INFRA-6173) Access to buildbots

     [ https://issues.apache.org/jira/browse/INFRA-6173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gavin closed INFRA-6173.
------------------------

    Resolution: Later

The ATS project moved its builds away from Buildbot so this access is no longer needed.
                
> Access to buildbots
> -------------------
>
>                 Key: INFRA-6173
>                 URL: https://issues.apache.org/jira/browse/INFRA-6173
>             Project: Infrastructure
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: Buildbot
>            Reporter: Igor Galić
>
> Hi folks,
> the Apache Traffic Server PMC has a number of buildbots configured. Many of them are "special", in that they don't match any active developers' development setup. When a buildbot fails, it is in the interest of the project to find out as quickly as possible why that is.
> Unfortunately, right now, only two of our PMC members (igalic, postwait) have access to the Solaris buildbot. (And while Solaris has been a sore spot for a long, it is now offline, which I suppose is a whole different story).
> Our project would like to take a more active approach: By having a trusted view members which have direct access to the buildbots, we could, for instance, take a look at coredump generated by the buildbot.
> I have asked Gavin a number of times on IRC, even offered bribes in the form of Whiskey. I am still ready to follow through with the latter. I am only bringing this up here, so it cannot get lost in the noise of IRC.
> So long,
> i

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira