Thanks! -----Original Message----- From: Mats Wichmann [mailto:m...@wichmann.us] Sent: Tuesday, September 26, 2017 1:37 PM To: Alex Kelley <ale...@microsoft.com>; iotivity-dev@lists.iotivity.org Subject: Re: [dev] Status of Jenkins
On 09/26/2017 02:26 PM, Alex Kelley wrote: > Thanks for the info Mats! > > Do you know if all of the machines are supposed to have the update at this > time? After the banner disappeared I retriggered a build that had a failure. > It just failed again and it appears to be due to the same issue of the > machine being out of room. Here is a link to the console output: > > https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbuild > .iotivity.org%2Fci%2Fjob%2Fiotivity-verify-tizen_unsecured%2F3089%2Fco > nsole&data=02%7C01%7Calexke%40microsoft.com%7Cca9b1949055d48fa61bb08d5 > 051e49ae%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C6364205500121578 > 95&sdata=w7Mxw1m4VxHNca9nlfB5v238v2WdGu09gvITAkmheas%3D&reserved=0 > > A couple of other times where Jenkins needed to be restarted I saw emails go > out to the dev alias indicating that it was going to happen. Is it part of > our policy to send out emails for when Jenkins is down or needs to go down? > If not I think it is something we should consider adding just so everyone has > an idea of what is happening. if they were scheduled, yes there's been announcements. this time stuff got killed that was going to fail anyway. I think I caused this one by yelling too loudly :) The best way to get a reaction to a builder problem is by filing a ticket - which happens by sending email to: IoTivity Helpdesk via RT <iotivity-helpd...@rt.linuxfoundation.org> however, that doesn't necessarily have wider visibility to the iotivity developers. I think there's some kind of status location one can check, I'll try to dig that out and share if I find it. _______________________________________________ iotivity-dev mailing list iotivity-dev@lists.iotivity.org https://lists.iotivity.org/mailman/listinfo/iotivity-dev
