Hi Konstantin, I am seeing two type of failures:
1) Maven download errors that don't show (afaics) any hint about what failed. Example: https://ci.bigtop.apache.org/view/Packages/job/Bigtop-trunk-packages/COMPONENTS=kafka,OS=centos-7-ppc64le/lastBuild/console 2) Connect timeouts while downloading poms, example: https://ci.bigtop.apache.org/view/Packages/job/Bigtop-trunk-packages/COMPONENTS=hive,OS=debian-10-ppc64le/lastBuild/console Usually 2) seems to be related to apache.org-related repo servers. I am not very expert with Maven but I was wondering how Bigtop releases were cut with such a degree of unpredictability in builds (if some secret option was used etc..). I naively thought that adding a basic retry to Maven would have improved the end result, but over time a lot of people (like Olaf mentioned) tried to resolve this problem so I preferred to ask first, before making silly suggestions :) Thanks, Luca On Mon, Jan 31, 2022 at 2:21 PM Konstantin Boudnik <[email protected]> wrote: > > Hey Luca. > > Did you notice if this is happening with some specific repo server? > > Tahnks! > Cos > > On Sat, Jan 29, 2022 at 08:31AM, Luca Toscano wrote: > > Hi everybody, > > > > I have been seeing build failures for trunk packages due to maven > > network failures (mostly connection timeouts). Is there a workaround > > for this? For example retrying x times etc.. I am asking mostly > > because of ignorance, I am wondering what we do when cutting a release > > for example (to avoid re-running the main package build job due to > > some package build failures). > > > > Thanks! > > > > Luca
