Tracking developer build times to decide if the M3 MacBook is worth upgrading

Re:Tracking developer build times to decide if the M3 MacBoo... by mewpmewp2 on Friday December 29, 2023 @08:56PM (#38812235)

You would need a very perfect and flexible CI system in place that wouldn't need to rebuild anything it doesn't need and only run the tests you want or only recently failed tests etc.

Many CI systems would spin up a new box instead of using persistent so likely have to rebuild if no cache, etc.

So basically I would say most of the overhead is in not having a persistent box with knowledge of last build or ability to choose what to run in there, which pretty much just equals to local capabilities.

[ Parent | on HN ]

Re:Tracking developer build times to decide if the M3 MacBoo... by peanball on Saturday December 30, 2023 @02:46AM (#38813493)

Often you also have the CI system designed in a way to verify a “from scratch” build that avoids any issues with “works on my machine” scenarios due to things still being cached that shouldn’t be there anymore.

[ Parent | on HN ]

Re:Tracking developer build times to decide if the M3 MacBoo... by jayd16 on Saturday December 30, 2023 @11:19PM (#38821761)

Having persistent boxes with sticky sessions seems seems pretty achievable.

[ Parent | on HN ]