On Sat, 10 Dec 2022 at 00:48, Greg Stein <gst...@gmail.com> wrote: > > On Fri, Dec 9, 2022 at 5:41 AM Olivier Lamy <ol...@apache.org> wrote: >> >> Hi >> Are we seriously activating this gradle enterprise to every build and >> so breaks a few builds without any notice? > > > Apologies. We thought it would simply be an additional output, and would not > affect any builds. Gaven has turned it off, and we'll do some more testing to > find out why this happened.
No worries. issues can happen but when something is touching builds, it's probably better to announce it. I don't understand why you guys INFRA do not talk first to the opensource communities of Maven and/or Jenkins if you need data on what is happening? Maybe those opensource communities can help you rather than talking to a commercial entity. > > >... >> >> [INFO] Publishing build scan... >> [INFO] https://ge.apache.org/s/mabitou3lbw2y >> >> we (Apache Maven) don’t want to use this > > > I see no discussion on dev@maven or private@maven to suggest the PMC does not > want this tool, once we get it debugged. Ah yes sorry for using this `we` whereas I just discussed it with folks on slack and didn’t have time to start some discussion on any @maven as this was breaking all our builds. so let's say we (some members of Apache Maven). Sorry for the emotional reaction! But imagine if infra was pushing some git toolinh behind the back of subversion guys and it even broke their build because of those git tooling (I'm sure you can understand such a reaction ;)). > > Regards, > Greg Stein > Infrastructure Administrator, ASF >
