On Sun, Jan 6, 2019, 19:52 Allen Wittenauer <a...@effectivemachines.com.invalid wrote:
> > > > On Jan 6, 2019, at 10:43 AM, Dominik Psenner <dpsen...@gmail.com> wrote: > > > > On Sun, Jan 6, 2019, 19:32 Allen Wittenauer > > <a...@effectivemachines.com.invalid wrote: > > > >> > >> a) The ASF has been running untrusted code since before Github existed. > >> From my casual watching of Jenkins, most of the change code we run > doesn’t > >> come from Github PRs. Any solution absolutely needs to consider what > >> happens in a JIRA-based patch file world. [footnote 1,2] > >> > > > > If some project build begins to draw resources in an extraordinary > fashion > > it will be noticed. > > Strongly disagree. My cleaner code killed three stuck surefire > jobs that had been looping on a handful of cores since sometime in 2018 > yesterday. Then those jobs surely exceed a resource, namely 'expected job runtime'. To me resources can be about anything as long as there are means to measure that resource. I wanted to say that build jobs should be monitored and eventually be killed if they exceed their quota of time, ram, disk, network, .. Do we have means to monitor resources that build jobs consume? That would be an essential tool to monitor the quality of this service. Having that data we could plot colorful charts in realtime with a tool like grafana. >
