If you want to try and implement a cache I would not be against it. I was just throwing my opinion into the ring. I don't know how much time you or another developer has to implement that type of system.
If we could get similar savings to the MangoDB guys (they saved almost 16 min per build) I think everyone would be interested in that. Like I said my biggest worry are builds that pass when they should not. George -----Original Message----- From: iotivity-dev@lists.iotivity.org [mailto:iotivity-dev@lists.iotivity.org] On Behalf Of Mats Wichmann Sent: Wednesday, October 31, 2018 1:07 PM To: iotivity-dev@lists.iotivity.org Subject: Re: [dev] caching build objects in scons On 10/30/18 4:59 PM, Mats Wichmann wrote: > On 10/30/18 4:21 PM, Nash, George wrote: >> Using a cached build sounds like a good idea on paper. as I continued the discussion of the general topic on the scons forum, a developer who implemented caching for the build of MongoDB, which is built using SCons, shared this diagram of their CI build times before-and-after. Hope the link works: https://pairlist4.pair.net/pipermail/scons-users/attachments/20181031/612e5743/attachment-0001.png -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#10000): https://lists.iotivity.org/g/iotivity-dev/message/10000 Mute This Topic: https://lists.iotivity.org/mt/27787640/21656 Group Owner: iotivity-dev+ow...@lists.iotivity.org Unsubscribe: https://lists.iotivity.org/g/iotivity-dev/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
