Closed AiyionPrime closed 6 years ago
Do you think it would be helpful if we had a BUILD_ONLY_BROKEN_TARGETS
flag in the gluon build scripts?
Didn't know that was a thing. Yes i like the idea. We could reduce build time by deploying the stable unbroken targets in the experimental folder as well.
Maybe we should introduce another "firmware branch" for this. I think experimental should be available for testing stuff like ddhcpd
or #7
Maybe a branch called "broken"?
I'd leave this here for another 16 hours, then create a new branch. How about we have a look at how much effort this costs midterm; and decide whether we keep it on the 13th april?
Once we have a distributed build environment, build extra stuff like this may be a useful utilisation.
Would be great if the more stable channels are always released in the less stable channels as well. e.g. if a new beta is released, it should be flashed to all devices on experimental channel as well and if a new stable is released, it should be flashed to all devices on experimental and beta, too.
Concerning the original question: Yes, build broken targets once in a while sounds good, since many of these aren't really broken, but just not tested.
No, that would not always be great. While we're testing e.g. new mesh-modules we do not want the test beeing interrupted by gluon-18d.
With beta this would mostly be fine, but experimental should not even neccessary be a channel, where routers stay for long. In my opinion it would be more useful if users had to opt in for a specifc experiment. (And had in return a better overview over their devices performance.)
Broken targets are now daily built in nightly branch: https://build.ffh.zone/job/gluon-nightly/ws/
Closing.
We came to the conclusion it might be nice to build broken targets as experimental every once in a while.
1977er what do you think about this?