Il 09/07/2014 20:45, Fabian Deutsch ha scritto: > Hello, > > I just wanted to give a short update on the state of the ovirt-appliance and > ovirt-node-iso for 3.5. > > ovirt-node is actually in a quite good shape. An iso is available with the > ovirt-node-plugin-vdsm and -hosted-engine. Both based on ovirt-node from > master, which will be branched off. > The pain point is the automation. > Ryan has actually gotten the Jenkins job back into place - good job! - so > that at least the rpm packages are built. And could actually be included in > the nighlies, Sandro.
Thanks for the update Fabian, can you list jobs to be added for each publisher? - publish_ovirt_rpms_nightly_3.4 - publish_ovirt_rpms_nightly_3.5 - publish_ovirt_rpms_nightly_master Or as it seems better from yesterday mail from rbarry, do you think it's better to have a - publish_ovirt_node_nightly_3.0 - publish_ovirt_node_nightly_3.1 publishing to something like http://resources.ovirt.org/pub/ovirt-node-base-3.0-snapshot http://resources.ovirt.org/pub/ovirt-node-base-3.1-snapshot > > The automatic iso generation is still not working, due to several reasons > (same as the last N months). > > The appliance generation is in a slightly better state than the > ovirt-node-iso generation, but is still failing when it comes to automation. > The automation is currently blocked by several issues which I tried to tackle > together with David during the last week. The build automation of the > appliance is actually getting most of my attention these days, as it is more > likely to get the automation working. > > So we are not stable yet, but we are moving into the right direction. > > Greetings > fabian > -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com _______________________________________________ Devel mailing list [email protected] http://lists.ovirt.org/mailman/listinfo/devel
