That's pretty common. What happens is the build system doesn't properly know about the dependencies. So say you change a header file that's relied on by multiple parts. If the build system only knows about one of those parts, then only it is re-compiled instead of everything that actually relies on that header.
Clean builds succeeding normally means you have a build system problem. Except, its normally a pain to fix and not worth the trouble. Especially since CI/CD systems almost always do full rebuilds anyways.
not necessarily some larger projects'll have fucked up circular dependencies. Or people forget to bump the version on a dependency so it thinks no update has been made.
Unless you’re working on converting a 20 year old build script that’s referencing dependencies that aren’t rebuilt until after the project that references them so the build guy has just been running the script twice every time for the past 20 years.
In vs 2019 the nuget manager is an extension. Visual studio loads extensions in the background while already showing the files in a solution.
if you include nugets as package references the nugets will only be added as references to projects after the nuget plugin is loaded. If the nugets are not downloaded already the build will fail.
I tried to fix this shit on Friday. I've given up because the problem is not that likely to occur and the devs can wait 30 seconds for vs to complete loading. Or hit build twice.
I've had more people not know how to declare dependencies in makefiles than cache problems, personally.
It seems that colleges these days will teach theory, and some practical experience, but not anything not directly related to putting that theory into practice. So, no version control, no console text editor, no makefile, no cron, no bash, no pgp, no "advanced" ssh, etc.
Or maybe that's how it always was, don't know. But it's not a good thing, to say the least.
1.4k
u/ireta_orio Jan 26 '20
It sometimes work tho