On 14-06-03 10:32 AM, Gabor Krizsanits wrote: >> >> It's pretty rare that things such OS, Compiler, SDK change on our build >> systems. We do tend to make noise about them when that happens, too. Do >> you have specific examples to point at? > > Where can I follow these changes? One specific example is bug 1002729 and the > like... > Currently m-c does not build with gcc 4.6 on ubuntu because something > similar. After > updating to 4.8 I got some warning in webrtc code, so I had to turn off > warning-as-errors. > > In the past we changed required windows SDK unannounced too... That being > said I can > totally imagine that I don't follow the right channels where these kind of > changes > are announced. For example, do we have a way to tell the exact configurations > on the > try server? Like exact gcc version / linux version...
The best place to self-serve this sort of information is probably the mozconfigs. Eg: https://mxr.mozilla.org/mozilla-central/source/browser/config/mozconfigs/linux32/nightly https://mxr.mozilla.org/mozilla-central/source/browser/config/mozconfigs/win32/nightly (Note that there's a chain of includes you need to follow.) It looks like you're right that these weren't called out anywhere. We used to blog about this sort of thing on planet, it looks like we don't do that in every case now. >> >> In any case, it's good to keep in mind that Try follows mozilla-central >> in terms of build configuration and requirements -- which means it's >> inherently unstable. We make no guarantees about build requirements >> staying static for any period of time. > > That is understandable. But let's say I want to work on a similar > configuration as the > linux box on try, where can I check the exact environment on it to reproduce > something > similar? Once I have it, how will I know that I should update something on it > to match > what we have on try? The longer term solution to this is Docker or something similar. For now, there's no great answer. For short term things you can request a loan of a machine (which will be set up exactly like our build machines): https://wiki.mozilla.org/ReleaseEngineering/How_To/Request_a_slave Other than that, the reality of the process right now is "do your best to test locally, then test on try", I think. _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
