Hi, * Barros Pena, Belen <belen.barros.p...@intel.com> [150330 19:48]: > We are considering working on integrating Toaster with Jenkins as part of > the next Yocto Project release. Our thinking so far is collected in this > Bugzilla feature:
> https://bugzilla.yoctoproject.org/show_bug.cgi?id=7527 Ah, sounds really interesting. I've recently been thinking about how I should be able to benefit from toaster, as we're running out automated builds using Jenkins. > Any thoughts? Are we missing something? Are we going about it in a > completely wrong way? Sounds quite good to me. If there's some project configuration that needs to be done in Toaster, I'd appreciate if as much as possible could be retrieved from our current Jenkins setup (i.e. exported from the Jenkins plugin to Toaster). (Not least as we're running a couple of scripts to source the environment and handling some extra configurations needed; thus I'd assume we couldn't just take the freestyle Jenkins project talked about in b) of Alexandru 's first comment in #YOCTO-7527. I don't know if this is the right thread but a couple of other things that we really would need in order to fully be able to utilize this. 1) Some way of getting the built git branch shown in toaster. (As we discussed on YPDD in Düsseldorf together with Axis). We're building master and release branches for the same machine and image. 2) In the proposed bug, would toaser be able to recieve and handle toaster/build logs from different YP releases? Normally we've at least one active release branch, and possibly a master (or master-next) branch that's going to the next YP release. If possible, I'd like to visualize all this in the same Toaster instance. Apart from that, I think this is really interesting! Cheers, Anders -- Anders Darander ChargeStorm AB / eStorm AB -- _______________________________________________ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto