infra-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel Takamori (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (INFRA-16043) Requesting user accounts to Jenkins build monitor
Date Thu, 15 Feb 2018 19:41:00 GMT

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

Daniel Takamori resolved INFRA-16043.
-------------------------------------
    Resolution: Won't Fix
      Assignee: Daniel Takamori

> Requesting user accounts to Jenkins build monitor
> -------------------------------------------------
>
>                 Key: INFRA-16043
>                 URL: https://issues.apache.org/jira/browse/INFRA-16043
>             Project: Infrastructure
>          Issue Type: Task
>          Components: Jenkins
>            Reporter: Nandish Jayaram
>            Assignee: Daniel Takamori
>            Priority: Major
>
> Apache MADlib has a build monitor on Jenkins:
> https://builds.apache.org/user/riyer/my-views/view/MADlib-Monitor/
> Only one committer from Apache MADlib had access to the build monitor during the incubation
phase. Now that MADlib is a TLP, can more committers get access to the Jenkins infra? Many
PR/Master builds fail due to some Jenkins infra issues, and we will need access to fix them.
It is a lot harder to have green builds with only one committer having the permission to do
that.
> It's great if all MADlib committers get a Jenkins account. If not, and there are some
resource constraints, can at least the following committers get access for the time being:
> http://home.apache.org/phonebook.html?uid=njayaram
> http://home.apache.org/phonebook.html?uid=okislal
> http://home.apache.org/phonebook.html?uid=fmcquillan



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message