gluster 3.1 is going to be forked from ovirt-engine-3.5, using a new branch.
a new job should be added via yaml (jenkins job builder), similar to
an infra engineer can assist with bootstrapping this job.
once the job is added, it needs to be added to the publisher of 3.5, and we need to make sure it's target dir isn't conflicting with existing ovirt-engine builds.
after this job is done, we'll continue to adding other sanity jobs.
I guess this was assigned by mistake to sbose. Moving to Sahina, let me know if you need help.
- is this still relevant?
No.there's already a nightly job - http://jenkins.ovirt.org/job/ovirt-engine_3.5-gluster_create-rpms_merged/
We can disable this nightly build, but leave the job with provision to build on manual trigger.
job removed from nightly builds.
keeping as manual trigger.