Is this verification job locked to a speciific POD or runnable in all CI PODs deployed by APEX?
On Tue, Dec 6, 2016 at 7:13 PM Ryota Mibu <[email protected]> wrote: > Hi, > > > > Let me explain current status in today’s meeting. > > > > > > BR, > > Ryota > > > > *From:* Carlos Goncalves [mailto:[email protected]] > *Sent:* Monday, December 05, 2016 11:52 AM > *To:* Yujun Zhang <[email protected]>; Mibu Ryota(壬生 亮太) < > [email protected]>; [email protected] > *Subject:* RE: [opnfv-tech-discuss] [doctor] doctor CI now available > > > > Yujun, it still cares for further (human) validation before we can make it > voting – the email I sent earlier shows that it’s not 100% ready yet. > > > > Carlos > > > > *From:* [email protected] [ > mailto:[email protected] > <[email protected]>] *On Behalf Of *Yujun Zhang > *Sent:* 05 December 2016 02:00 > *To:* Ryota Mibu; [email protected] > *Subject:* Re: [opnfv-tech-discuss] [doctor] doctor CI now available > > > > Nice job! > > > > One comment inline. > > > > On Sun, Dec 4, 2016 at 3:55 PM Ryota Mibu <[email protected]> wrote: > > Hi, > > > Doctor CI jobs are now available and I confirmed those returns green > lights with current codes on the master branch. > > Reviewers, please check the CI results before merging a patch set. > > > > So the verification job is not voting? Why not? > > > > If the CI jobs were run before Dec 2nd, just trigger CI jobs again by > leaving comment "recheck". > > doctor-verify-apex-sample-master > doctor-verify-apex-congress-master > > Note: congress works fine, with some quick hack on the POD after I > installed OPNFV with latest apex. I'll work with apex team to fix issues I > found. > > Let me know if you find any problems in those CI jobs. > >
_______________________________________________ opnfv-tech-discuss mailing list [email protected] https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
