Re: [cbi-dev] Something killing my build on clustered CI
|FYI, I've added an entry to the Jenkins FAQ https://wiki.eclipse.org/Jenkins#What_is_killing_my_build.3F_I.27m_using_custom_containers.21|
Team Lead - Release Engineering | Eclipse Foundation
📱 (+33) 642 028 039 | 🐦 @mikbarbero
The “memory” one should be set to set however much memory your build process needs + some overhead. I arrived at the numbers for CDT by trial and error, basically just keep decreasing a bit at a time until it starts failing. We found out that by default projects will have a total limit of 4GB total for custom containers, so setting this to > 2GB will restrict you to 1 build at a time. For “cpu” you can probably just set this to “1”, we only needed to go higher for CDT as some of our UI tests crashing with less. Generally just the “requests” & “limits” values to be the same.
Thank you very much William! You saved me many hours if I had to figure out that by myself.
I've copied what I interpret as "black magic random numbers" (I don't know much practical details about Kubernetes) in my Jenkinsfile and it works as expected.
Renesas Electronics Europe GmbH,Geschaeftsfuehrer/President : Olav Schulte, Sitz der Gesellschaft/Registered office: Duesseldorf, Arcadiastrasse 10, 40472 Duesseldorf, Germany,Handelsregister/Commercial Register: Duesseldorf, HRB 3708 USt-IDNr./Tax identification no.: DE 119353406 WEEE-Reg.-Nr./WEEE reg. no.: DE 14978647_______________________________________________cbi-dev mailing listcbi-dev@xxxxxxxxxxxTo change your delivery options, retrieve your password, or unsubscribe from this list, visithttps://www.eclipse.org/mailman/listinfo/cbi-dev
Description: Message signed with OpenPGP