My question was why do we need the build artifacts for e.g?I'm OK with the check-patch jobs that verify compilation for e.g, but are we using the 3.6.2 build artifacts jobs?
e.On Wed, Jan 13, 2016 at 9:59 AM, Sandro Bonazzola <sbonazzo@redhat.com> wrote:On Wed, Jan 13, 2016 at 8:22 AM, Eyal Edri <eedri@redhat.com> wrote:I can't recall which 3.6.2 jobs we said we'll keep and which we'll drop.IIRC, we don't need the build artifacts jobs [1]Tal, you mentioned there were some jobs you do want to see running on the version branch,Do you recall which?I remind that running these temporarily jobs is an overhead since its temporal and are a subset of the 3.6 jobs, so chance of hitting something there which didn't fail on the 3.6 is slim.3.6.2 jobs are needed only until Jan 26th when we'll release 3.6.2 GA. Then we can get rid of all of them.--Eyal Edri
Associate Manager
EMEA ENG Virtualization R&D
Red Hat Israel
phone: +972-9-7692018
irc: eedri (on #tlv #rhev-dev #rhev-integ)--Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com--Eyal Edri
Associate Manager
EMEA ENG Virtualization R&D
Red Hat Israel
phone: +972-9-7692018
irc: eedri (on #tlv #rhev-dev #rhev-integ)