When we create a release branch, the Maven build in the develop branch usually ends up in a bad state until it gets manually cleaned up. I think the build server is trying run Maven on the develop branch once per day, and it fails because it hasn't been cleaned up yet.
As I recall, the version number in some (but not all) of our pom.xml files doesn't get updated automatically, causing a mismatch that triggers the failure. -- Josh Tynjala Bowler Hat LLC https://bowlerhat.dev/ On Thu, Nov 12, 2026 at 9:34 AM Andrew Wetmore <[email protected]> wrote: > The Infra build servers are at 95% capacity, and Royale is on the list of > high-volume users: > > [image: image.png] > > I see repeated 'build failed!' messages and have been presuming those are > related to different builds related to a variety of work, but am I wrong? > Is this a run that keeps failing and then repeating? > > There is a bunch of advice to help projects cut down on their resource > use. Have you guys been following those threads? > > a > > > Andrew Wetmore > Assistant VP, Marketing and Publicity, The ASF <https://apache.org> > Editor-Writer, Infra team, The ASF > > Editor, moosehousepress.com > > > <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail> > Virus-free.www.avast.com > <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail> > <#m_8288543755168220561_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> >
