Hello all, I have reached today the milestone of being able to trigger a build to run under toaster web control.
I have pushed by branch for review here: adamian/20140530-bldcontrol The UI interface (last two commits) is not ready for merging. It is there just as a starting point for design / illustrate the command model. The rest of the patches are targeted at review for merging. I am currently testing them, and probably I will have one more review iteration before submitting upstream. I want to make sure that you don't see any major architectural / code issue with how things are designed now. -- How to use: - the normal "source toaster start" mode for logging interactive shell builds is preserved and should be working normally. - if you run, after source checkout, "bitbake/bin/toaster" (i.e. run the script instead of sourcing it, and with no oe-init-build-env !) , toaster starts in the managed mode. The toaster web server will start in the current directory, and your browser will be pointed to the home page. - in the home page, upper left corner, a new link "New Build" will lead you to the build trigger page; enter your target and press Submit. - if all goes well, a managed build will start in the "build/" directory. There is a slight delay while the system runs through the queues. Your machine load will rise, and the build will be reflected in the web interface. - when the build is done, toaster will stop the bitbake server, but the build/ directory is preserved. I'm awaiting your feedback, Alex -- Alex Damian Yocto Project SSG / OTC
-- _______________________________________________ toaster mailing list [email protected] https://lists.yoctoproject.org/listinfo/toaster
