[ACTION REQUIRED] ovirt-node-plugin-vdsm_master_create-rpms_merged
Hi, Comparing 3.4 and master publisher I see that ovirt-node-plugin-vdsm_master_create-rpms_merged is collected by 3.4 publisher and not by master publisher. Can you take a look and verify that master branch is intended to be in 3.4.3 RC and it's not needed anymore in 3.5/3.6 ? Thanks, -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com
On 07/09/2014 04:36 AM, Sandro Bonazzola wrote:
Hi, Comparing 3.4 and master publisher I see that ovirt-node-plugin-vdsm_master_create-rpms_merged is collected by 3.4 publisher and not by master publisher. Can you take a look and verify that master branch is intended to be in 3.4.3 RC and it's not needed anymore in 3.5/3.6 ? Thanks,
This really requires a response from dougsland, since I haven't kept up on the versioning, but there's another job (ovirt-node-plugin-vdsm_node-3.0_layered_merged) which generates RPMs from the 3.0 branch to be used, and I'd suspect that's what should be in the 3.4 publisher.
On 07/09/2014 10:57 AM, Ryan Barry wrote:
On 07/09/2014 04:36 AM, Sandro Bonazzola wrote:
Hi, Comparing 3.4 and master publisher I see that ovirt-node-plugin-vdsm_master_create-rpms_merged is collected by 3.4 publisher and not by master publisher. Can you take a look and verify that master branch is intended to be in 3.4.3 RC and it's not needed anymore in 3.5/3.6 ? Thanks,
This really requires a response from dougsland, since I haven't kept up on the versioning, but there's another job (ovirt-node-plugin-vdsm_node-3.0_layered_merged) which generates RPMs from the 3.0 branch to be used, and I'd suspect that's what should be in the 3.4 publisher. Correct.
3.4.x the branch is node-3.0 (The same branch name as ovirt-node project). -- Cheers Douglas
participants (3)
-
Douglas Schilling Landgraf -
Ryan Barry -
Sandro Bonazzola