Skip to main content
6 events
when toggle format what by license comment
Mar 7, 2017 at 8:43 comment added Voo @immibis You did read the part in parens right after the part you quoted? It is a worst case scenario if a build server is involved. The problem with non reproducible bugs is that you can't really do Hotfixes if your whole build environment changed in the meantime. That isn't much of a problem if you only have a single released version that's kept close to trunk, but in all other cases it's pretty bad.
Mar 7, 2017 at 7:37 comment added Stack Exchange Broke The Law @Voo It's hardly a worst case scenario, it's a middle case scenario. What the asker currently has is a worst case scenario. (Also note that if you never reproduce builds, random compiler upgrades aren't too much of a problem)
Mar 4, 2017 at 0:23 comment added Voo Agreed on wanting to have a automatic process for creating new builds, but at the same time you also want to virtualize your build agents to make sure your build environment is under your own control. VMs are an amazing tool for dev ops and you should make the most of it.
Mar 4, 2017 at 0:20 comment added Voo "You say that like it's a bad thing. You now have a common build server that all of your builds - yours and the other teams' - are built through. Consistency of build? Check". That's the complete opposite of a consistent build! If any other team decides to update their compiler or any other tool you're suddenly dealing with a completely different build environment. That's pretty much a worst case scenario (apart from not having a build machine to begin with).
Mar 3, 2017 at 21:46 comment added jpmc26 "You say that like it's a bad thing." It could be if they have free reign to install whatever junk they want. If they're remoting in or physically accessing it, I don't see how that could be prevented.
Mar 3, 2017 at 15:24 history answered Phill W. CC BY-SA 3.0