From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga04.intel.com (mga04.intel.com [192.55.52.120]) by dpdk.org (Postfix) with ESMTP id 09C2E3777 for ; Tue, 15 Nov 2016 10:07:53 +0100 (CET) Received: from orsmga003.jf.intel.com ([10.7.209.27]) by fmsmga104.fm.intel.com with ESMTP; 15 Nov 2016 01:07:53 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.31,641,1473145200"; d="scan'208,217";a="901535545" Received: from fmsmsx104.amr.corp.intel.com ([10.18.124.202]) by orsmga003.jf.intel.com with ESMTP; 15 Nov 2016 01:07:52 -0800 Received: from fmsmsx120.amr.corp.intel.com (10.18.124.208) by fmsmsx104.amr.corp.intel.com (10.18.124.202) with Microsoft SMTP Server (TLS) id 14.3.248.2; Tue, 15 Nov 2016 01:07:52 -0800 Received: from shsmsx104.ccr.corp.intel.com (10.239.4.70) by fmsmsx120.amr.corp.intel.com (10.18.124.208) with Microsoft SMTP Server (TLS) id 14.3.248.2; Tue, 15 Nov 2016 01:07:52 -0800 Received: from shsmsx102.ccr.corp.intel.com ([169.254.2.239]) by SHSMSX104.ccr.corp.intel.com ([169.254.5.142]) with mapi id 14.03.0248.002; Tue, 15 Nov 2016 17:07:48 +0800 From: "Xu, Qian Q" To: "ci@dpdk.org" Thread-Topic: Could we have some agreements on the CI then discuss the opens Thread-Index: AdI/H7t1V/x2hVOVRI+BXtzZGywrXA== Date: Tue, 15 Nov 2016 09:07:48 +0000 Message-ID: <82F45D86ADE5454A95A89742C8D1410E39258B31@shsmsx102.ccr.corp.intel.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.239.127.40] Content-Type: multipart/alternative; boundary="_000_82F45D86ADE5454A95A89742C8D1410E39258B31shsmsx102ccrcor_" MIME-Version: 1.0 Subject: [dpdk-ci] Could we have some agreements on the CI then discuss the opens X-BeenThere: ci@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: CI discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Nov 2016 09:07:54 -0000 --_000_82F45D86ADE5454A95A89742C8D1410E39258B31shsmsx102ccrcor_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi, all I just think that if we can have some agreements on the DPDK CI tasks first= ly, then discuss about the open list. Possible agreement parts: 1. Schedule tool: Jenkins. LF has the Jenkins as the schedule tool. So I wonder if all agree on this s= chedule tool for scheduling build and regression test. 2. Create per patch check(patchcheck and build) by using Jenkins to tr= igger For each patch check, currently we cover the Patchcheck and build. I noticed Thomas has a separate mail about checkpatch, so does it mean we c= an remove patchcheck from the build test? For build test, Intel can provide Intel IA based per patch build report. If= there is common format, we can follow it. 3. Create daily or weekly functional/build regression test based on gi= t tree, also using Jenkins to trigger For the functional/build regression tests, Intel has already sent out the d= aily build and functional regression test. If there is common format, we ca= n also follow it. Besides Intel, I have also seen the IBM's daily build report. Any others wa= nt to publish the daily/weekly functional regression tests? Opens: 1. Centralized or distributed performance lab. Is the decision more de= pendent on budget or the thoughts? 2. Performance report center. Do you want to publish the performance r= eport and which is the preferred format? 3. The code review tool is still by mailing list. Is it the final deci= sion? 4. How about the central bug system? Do we want to have one? Proposal: Could we have a CI weekly sync-up meeting for discussion only on= CI? If most people on the mailing list from EU and PRC, then we could find= a more friendly time for PRC people. --_000_82F45D86ADE5454A95A89742C8D1410E39258B31shsmsx102ccrcor_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hi, all

I just think that if we can have some agreements on = the DPDK CI tasks firstly, then discuss about the open list.  

Possible agreement parts:

1.      Schedule tool: Jenkins.

LF has the Jenkins as th= e schedule tool. So I wonder if all agree on this schedule tool for schedul= ing build and regression test.

 

2.      Create per patch check(patchcheck and build) by usi= ng Jenkins to trigger

For each patch check, cu= rrently we cover the Patchcheck and build.

I noticed Thomas has a s= eparate mail about checkpatch, so does it mean we can remove patchcheck fro= m the build test?

For build test, Intel ca= n provide Intel IA based per patch build report. If there is common format,= we can follow it.

 

 

3.      Create daily or weekly functional/build regression = test based on git tree, also using Jenkins to trigger

For the functional/build= regression tests, Intel has already sent out the daily build and functiona= l regression test. If there is common format, we can also follow it.

Besides Intel, I have al= so seen the IBM’s daily build report. Any others want to publish the = daily/weekly functional regression tests?

 

Opens:

1.      Centralized or distributed performance lab. Is the = decision more dependent on budget or the thoughts?

2.      Performance report center. Do you want to publish t= he performance report and which is the preferred format?  <= /p>

3.      The code review tool is still by mailing list. Is i= t the final decision?

4.      How about the central bug system? Do we want to hav= e one?

 

Proposal:  Could we have a CI weekly sync-up me= eting for discussion only on CI? If most people on the mailing list from EU= and PRC, then we could find a more friendly time for PRC people.

--_000_82F45D86ADE5454A95A89742C8D1410E39258B31shsmsx102ccrcor_--