-
Christian Dietrich authored
Since we have problem we heavily merging in build histories (cpython), We now try a more robust variant for each commit: 1. Build the parent 1.a) Last Build was the parent, and that was good -> Do nothing 1.b) Last Build not the parent. git reset and build A) was ok? fine B) rebuild failed -> git clean, reset, try again 2. Build the commit itself We always try to build children first to avoid heavy jumping between different banches and commits. But that is only an optimization. Lets give it a try.
4c715b34