On Sep 5, 2012, at 10:30 , Michael Haberler wrote: > > Am 05.09.2012 um 18:03 schrieb Sebastian Kuzminsky: > >> If there is any additional information that you think would be useful there, >> let me know and I'll add it! > > yes: it would help to point to either some text describing, or point to a git > repo containing the configuration files which drive the first compile, and > pbuilder, to the extent you could actually replicate a tripped build locally.
I don't want to publish the buildbot configs directly, because they contain the passwords that the buildslave use to connect to the buildmaster, with this information it's trivial to bring down the buildbot. But luckily the information about what exact commands are run is already available, in somewhat cryptic and hard-to-find form. I added a chunk to the buildbot dev webpage called "Debugging failed builds", see if that has what you asked for. > For instance, fixing amd64 aligment issues like we just had are a shot in the > dark when you dont have the compile environment, and no recipe to replicate. > > Is it common practice to push a development branch to git.linuxcnc.org to > exercise the build? Back when I was doing a lot of linuxcnc development, I often pushed dev branches to the buildbot to test them. Once I got them working I'd rebase them to clean up my messy history, rebase them onto master (or 2.5 or whatever branch they were going to go in), push one last time to make sure i didn't mess anything up, then push them to the target branch. This workflow is nice because it keeps the official branches working, and keeps their history clean. Hm, I think i'll add a chunk to the buildbot dev webpage with this info on it too, hold on…. Ok done! -- Sebastian Kuzminsky ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Emc-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-developers
