Allen, > On 10 Feb 2017, at 6:34 am, Allen Wittenauer <a...@effectivemachines.com> > wrote: > > >> On Feb 9, 2017, at 10:45 AM, Pedro Giffuni <p...@apache.org> wrote: >> >> With minotaur also decommissioned I am feeling less interest to >> spend time on Apache projects. > > Same. The continual shut down of non-Linux, non-Windows machines has > been a major deterrent to spending time on ASF projects.
Name all the non-Linux, non-Windows machines that we have shut down that affected you and your project directly please, Im interested to know. I’m very interested in hearing how the shut down of these has negatively impacted your willingness to spend time on ASF projects. (What flavour OS you work on is up to you) > But it's been pretty clear over the past year where the focus has been, > given that machines were shut down despite having jobs actually being run on > them. If you are talking about Sonar Analysis we provided a better, quicker more up to date self-serve connected to LDAP version so you can just get on with configuring your own builds. Many projects have taken advantage of tweaking their existing Jenkins jobs to produce Sonar results with ease. We also gave many weeks notice so that you could migrate your job. What is your issue with this? Other than Sonar, what other machines do you know of that were shut down despite having jobs actually running on them? (You said ‘machines’ plural so it would be great to get the complete list to we have a bigger overview in how you and your project were affected) > It feels extremely short sighted, but whatever. Given our resources, budget, staffing and volunteer numbers, consolidation of OS flavours, puppetising of services has been a long sighted view IMHO > Projects should probably start pursuing corporate benefactors to support > non-ASF build infrastructure. Many projects already do. It is not compulsory to use ASF hardware for builds, we try to provide the best we can given the resources we have at our disposal. We have increased our Jenkins nodes to 47 and puppetised them all ensuring consistency, we have increased Buildbot nodes to over 20 , most of those too are puppetised. This makes it better for projects and better for us. We are also improving documentation for build services also [1] . All in all Allen, I’m a little disappointed that all the improvements to the builds systems over the last year and all I hear is complaints. So I’d like to pursue those complaints as it makes me sad, makes me feel I haven’t done my job right, that I have failed in my duties. Please do take the time to answer the queries above. (Note I say ‘I’ a lot in that last sentence, not speaking for the rest of the team here who have equally been improving the build services, but I would personally like this feedback. I take emails like yours and Pedros very seriously and very personally.) And a reminder to all that this builds@ mailing list is a publically archived mailing list [2] Thanks Gav… [1] - https://cwiki.apache.org/confluence/display/INFRA/Jenkins <https://cwiki.apache.org/confluence/display/INFRA/Jenkins> https://cwiki.apache.org/confluence/display/INFRA/Jenkins+node+labels <https://cwiki.apache.org/confluence/display/INFRA/Jenkins+node+labels> [2] - http://mail-archives.apache.org/mod_mbox/www-builds/ <http://mail-archives.apache.org/mod_mbox/www-builds/>
