Mailing-List: contact dev-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cloudstack.apache.org
From: Bharat Kumar <bharat.kumar@accelerite.com>
To: "dev@cloudstack.apache.org" <dev@cloudstack.apache.org>
Subject: Re: [PROPOSAL] Minimum Viable CI Integration
Thread-Topic: [PROPOSAL] Minimum Viable CI Integration
Thread-Index: 
 AQHRdbCjh8GiMZGAak211vRN2ht53p9IdoIAgAAKOQCAAAiuAIAAKN+AgAACuYCAAAfuAA==
Date: Fri, 4 Mar 2016 05:08:03 +0000
Message-ID: <5AF086EF-0A6E-45C4-ADB3-7508EEAABEC3@persistent.co.in>
References: 
 <CAC2panpb6AwaQL715_3rGjhxpHq4o7XJKEeD-Vecf8H-4Vu46w@mail.gmail.com>
 <CAC2panrEst_rs6OCTxVZyn1aP52prErBeAAc9-nua2FvZKUZ2w@mail.gmail.com>
 <CANqzcQvgymKCrkf8-x9Btx+XX7F8voMmYScub=q0=+4RtnPo4A@mail.gmail.com>
 <CAC2panrj6VH1_sWPhebJ1x+e66zO2UT_p-n0_ea05nzKbJ0Z6w@mail.gmail.com>
 <9EE3C485-68AE-49BF-9626-1A91C7C7CF87@persistent.co.in>
 <CAC2panrAQ-ehyF8eYxdMt0=pZ99kzoM3Zzyw8oC+hm48E_2ufA@mail.gmail.com>
In-Reply-To: 
 <CAC2panrAQ-ehyF8eYxdMt0=pZ99kzoM3Zzyw8oC+hm48E_2ufA@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
x-ms-exchange-messagesentrepresentingtype: 1
x-originating-ip: [121.240.161.130]
x-ms-office365-filtering-correlation-id: ed009291-75e0-43c9-35e0-08d343eaf77b
x-microsoft-exchange-diagnostics: 
 1;TY1PR04MB0894;5:pU8xnkwrP1wQAXX+rrOxDjz4t22shWIUaDp7EL+a2ZcaIx9MSSzWRaP2QacpnSKR/PtT2eOW4meiIchJTXdnX01OMtZnkc0w5HHsYdJbiIGGhRC5uRaSnCtYV89n+rZ0gDfvnQWgRoTX51RlauORcQ==;24:4a4oWSg01uoh+QIg/2aW7z8mCy8Igjw6wE9vefH74FhOTzWohmtIJRQTEopp/3OHEHvHQJPg16umdq6iqykFco3D7w1k0bnWRODbEOHzemY=
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:TY1PR04MB0894;
x-microsoft-antispam-prvs: 
 <TY1PR04MB0894EAF230C36F4A3A4C2E9DF0BE0@TY1PR04MB0894.apcprd04.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: 
 BCL:0;PCL:0;RULEID:(601004)(2401047)(5005006)(8121501046)(10201501046)(3002001);SRVR:TY1PR04MB0894;BCL:0;PCL:0;RULEID:;SRVR:TY1PR04MB0894;
x-forefront-prvs: 0871917CDA
x-forefront-antispam-report: 
 SFV:NSPM;SFS:(10009020)(6009001)(38564003)(51914003)(24454002)(377454003)(53754006)(69234005)(164054003)(189998001)(450100001)(3660700001)(10400500002)(86362001)(2351001)(3280700002)(87936001)(122556002)(81166005)(2906002)(40100003)(77096005)(15975445007)(36756003)(2501003)(66066001)(106116001)(5890100001)(5002640100001)(2950100001)(2900100001)(6116002)(92566002)(5008740100001)(19580395003)(5004730100002)(76176999)(54356999)(102836003)(3846002)(50986999)(586003)(110136002)(107886002)(1220700001)(1096002)(11100500001)(19580405001)(200143003)(104396002);DIR:OUT;SFP:1101;SCL:1;SRVR:TY1PR04MB0894;H:TY1PR04MB0893.apcprd04.prod.outlook.com;FPR:;SPF:None;MLV:sfv;LANG:en;
spamdiagnosticoutput: 1:23
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="us-ascii"
Content-ID: <225CD39196DDA34E8D0D286534E1473A@apcprd04.prod.outlook.com>
content-transfer-encoding: quoted-printable
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-originalarrivaltime: 04 Mar 2016 05:08:03.9545
 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 1f4beacd-b7aa-49b2-aaa1-b8525cb257e0
X-MS-Exchange-Transport-CrossTenantHeadersStamped: TY1PR04MB0894
X-OriginatorOrg: accelerite.com
X-Brightmail-Tracker: 
 H4sIAAAAAAAAA+NgFtrBJsWRmVeSWpSXmKPExsXCpfPHUddf4maYwayL6ha3HrM5MHrsa+5k
	CmCMamC0SczLyy9JLElVSEktTrZVckxOTs1JLcoECvikpifmKLhkFifnJGbmphYpKWSm2CqZ
	KCkU5CQmp+am5pXYKiUWFKTmpSjZcSlgABugssw8hdS85PyUzLx0WyXPYH9dCwtTS11DJTs1
	ZUNjay4gmfCeNWPH1ZCCPveK79edGxjPW3QxcnJICJhIfDp4iB3CFpO4cG89WxcjF4eQwBYm
	iZ8vPkI5hxgl3j6YygTisAjMZpa4cP86O0TmKqPE2umXWSGco4wSHdv7wIaxCRhITL7xjgXE
	FhGwlvjTt5YJxBYWMJV417mCESJuJtHy5jA7hB0m0f+ogRXEZhFQkeg+8RqsnlfAWeLn0x5G
	iAXLmCUeHXjPDJLgFAiUuPhzDtgCRqDLv59aA9bALCAucevJfCaIjwQkluw5zwxhi0q8fPwP
	7FJGgZWMEicXfoUq0pE4e/0JI4StLHHq2Uco21fi4unZYE9LCOxhkrh4qB1qkpvE5fYHrBB2
	tsSzSRPZIGwtiY4js6Aa1jNKfL3zFWqSjMSDw/dZIRJ7WSWePj3MDAkMKYnGPStZJjBqz0Jy
	OoStI7Fg9yc2CNtDYs21bywQtrbEsoWvmWeBw0ZQ4uTMJywLGFlXMcp4eOkG+4YE6PqHhugV
	pBYVZxaXAFOOXnK+XmbeJkZQ8tTlENzB2LNf/xCjAAejEg8v28cbYUKsiWXFlbnACOZgVhLh
	FeK+GSbEm5JYWZValB9fVJqTWnyI0QcYIxOZpUST8/NARsYbGltaWhqYmxkbmxka4hBWEue1
	f3EuTEggHZjks1NTgS6CGcfEwSnVwMhoOvHJvYg3n3auZ7h4wankmrBaU2Lcb9/gOTFvFVca
	HmO8kn1B6/ZMX1GN03Fn303b8Tq3Se/vgY12He5mNc9VmXmNfRmuu57f5fjgxvGJtdLreLoN
	XwaeniYb9a8mRXtxpZirU0hp0WyhauNNL00bl03xUkiX6vgc+zMr+6qXtVSTua7YKSWW4oxE
	Qy3mouJEAKKWJ3fLAwAA

Thanks for the info Will.

I also faced a similar problem. I will get back to you if i see any further=
 issues.

Thanks,
Bharat.  
 
> On 04-Mar-2016, at 10:12 AM, Will Stevens <williamstevens@gmail.com> wrote=
:
> 
> Awesome, thanks for the update Bharat, that is great progress.
> 
> If you need a hand with the posting back to the pull requests on github,
> just let me know, I have that piece working.  My implementation is a cross
> platform binary without any dependencies so it could be easy to integrate
> if that would be helpful.  I plan to clean it up a bit and open source it.
> I have only spent a few hours on it so far, so I want to do a once through
> to get it ready to release.
> 
> Just an FYI, it is not very easy to post back to github using the 'Pull
> Requests' API because of the code reference requirements.  Checkout the
> 'Issues' API which is basically the same thing, but enables you to create
> comments without having to specify a specific location in the PRs code
> which you are commenting on.  This tripped me up for a while today and onc=
e
> I realized I could do it through the Issues instead of the Pull Requests,
> it made things infinitely easier.
> 
> Let me know if you have other questions.
> 
> Cheers,
> 
> Will
> 
> 
> On Thu, Mar 3, 2016 at 11:29 PM, Bharat Kumar <bharat.kumar@accelerite.com=
>
> wrote:
> 
>> Hi will,
>> 
>> we have a solution to post the results to the community by email. We also
>> have a github integration to fetch the Prs , run tests against them and p=
ost
>> the consolidated results by email and share the logs using dropbox.
>> 
>> We are facing some setup delays to get this up and running. I am sure we
>> will be able to do this shortly.
>> 
>> I am also working on posting the results in PR as comments.
>> 
>> Thanks,
>> Bharat.
>> 
>> 
>> 
>>> On 04-Mar-2016, at 7:36 AM, Will Stevens <williamstevens@gmail.com>
>> wrote:
>>> 
>>> Last I knew Bharat did not have a solution for posting results back to
>> the
>>> community. I could be wrong though, I don't really know how complete a
>>> solution Bharat has at this point.
>>> 
>>> There are two other CI implementations in various states of completeness
>>> and I think it is important to have a common mechanism which will work t=
o
>>> post results back to the community regardless of the CI implementation.
>>> 
>>> "bubble" from SBP seems to be the most complete so far and has been used
>> to
>>> test over 100 PRs, but I don't think the results have formally
>> contributed
>>> back for the community to review.
>>> 
>>> "trillian" is a project shapeblue is working on, but I am still getting
>>> details for when it is expected to be operational.
>>> 
>>> This may not be a final solution, but I feel it is a good first step
>> which
>>> will be easy for everyone to work with.
>>> On Mar 3, 2016 8:35 PM, "Gandikota Srinivas" <
>> gandikota.srinivas@gmail.com>
>>> wrote:
>>> 
>>>> Will,
>>>> I guess Bharat has something similar in working.
>>>> 
>>>> Bharat,
>>>> Can you please elaborate your approach for sharing the CI results with
>>>> community ?
>>>> 
>>>> Thanks,
>>>> Srinivas
>>>> 
>>>> On Fri, Mar 4, 2016 at 6:28 AM, Will Stevens <williamstevens@gmail.com>
>>>> wrote:
>>>> 
>>>>> Apparently attached files don't work when sending to the mailing list.
>>>>> 
>>>>> Find the screenshot here:
>>>>> 
>>>>> 
>>>> 
>> https://objects-east.cloud.ca/v1/5ef827605f884961b94881e928e7a250/swill/S=
creen%20Shot%202016-03-03%20at%207.53.42%20PM.png
>>>>> 
>>>>> On Thu, Mar 3, 2016 at 7:54 PM, Will Stevens <williamstevens@gmail.com
>>> 
>>>>> wrote:
>>>>> 
>>>>>> Hey Everyone,
>>>>>> As I am sure most of you are aware, I have been focusing a lot on way=
s
>>>> to
>>>>>> get CI integrated back into the community.
>>>>>> 
>>>>>> Today I build a little POC to validate some ideas and get a feel for=
 a
>>>>>> potential approach for getting CI integrated into the Github pull
>>>> request
>>>>>> workflow.
>>>>>> 
>>>>>> There are multiple individuals/companies focusing on CI right now
>>>> (which
>>>>>> is a good thing), but there has not really been much discussion (that
>> I
>>>>> am
>>>>>> aware of) for how these different CI runs will push back results to
>> the
>>>>>> community.  I want to make sure that nobody's work on this topic goes
>>>> to
>>>>>> waste, so my goal is to provide a simple and consistent way for
>>>> everyone
>>>>> to
>>>>>> push their results back to the community.
>>>>>> 
>>>>>> Here is the basic idea (please give feedback):
>>>>>> - A simple cross platform command line tool with zero dependencies
>> will
>>>>> be
>>>>>> provided (and open sourced) which will handle the submission of the C=
I
>>>>>> results back to the community.  It is written in Golang and is
>>>> currently
>>>>>> called 'notify_pr'.
>>>>>> - At the end of a CI execution, the CI should automate the execution
>> of
>>>>>> this tool to handle updating the appropriate PR with the results.
>>>>>> 
>>>>>> Configuration can be done via the command line or through an INI file=
.
>>>>>> Here is an example of the configuration details.  The commit is the
>>>>>> commit that the CI just executed against.
>>>>>> 
>>>>>> token  =3D <your github token>
>>>>>> owner  =3D apache
>>>>>> repo   =3D cloudstack
>>>>>> commit =3D c8443496d3fad78a4b1a48a0992ce545bde299e8
>>>>>> 
>>>>>> summary_file =3D <a text file summary of the run>
>>>>>> full_detail_dir =3D <a directory structure to be recursively uploaded=
 to
>>>>>> object store>
>>>>>> full_detail_files =3D <a comma separated list of files to upload to
>>>> object
>>>>>> store>
>>>>>> store_api =3D <swift or s3>
>>>>>> store_endpoint =3D <url endpoint>
>>>>>> store_identity =3D <keystone identity or aws access key>
>>>>>> store_secret =3D <keystone password or aws secret key>
>>>>>> 
>>>>>> I have not yet implemented the object storage endpoints, but I have
>>>> code
>>>>>> to do it from a different project, so I just need to add it.  I will
>> be
>>>>>> able to host my CI output in a swift object store, but others may nee=
d
>>>> to
>>>>>> use AWS S3.  Maybe we can get sponsorship for this storage.  We will
>>>> only
>>>>>> keep the logs for a window of like a week or so on the object store s=
o
>>>>> the
>>>>>> storage usage will not be ever growing.
>>>>>> 
>>>>>> Basically, the tool takes the details of the repository you are
>>>>> validating
>>>>>> a Pull Request for and the commit you are building.  It also takes th=
e
>>>>>> files you would like to push to the pull request.  The summary file
>>>> will
>>>>> be
>>>>>> shown as text in the pull request comment and the other files will be
>>>>>> uploaded to an object store and will be publically available for a
>>>> period
>>>>>> of time (probably about a week and then get cleaned up, details TBD).
>>>>> The
>>>>>> files to be uploaded to object store could be either specified as
>>>>>> individual files, OR a target directory and all the files in that
>>>>> directory
>>>>>> will be recursively uploaded to the object store.
>>>>>> 
>>>>>> When the tool is run, it will scan through all the open pull requests
>>>> in
>>>>>> the target repository and when it finds the pull request correspondin=
g
>>>> to
>>>>>> the commit in question, it will post the details as a comment to that
>>>>> pull
>>>>>> request.  This functionality is currently working (see the attached
>>>>>> screenshot).  I can change the formatting and such, this is just an
>>>>> example.
>>>>>> 
>>>>>> This is still a very rough concept that I have only worked on for a
>>>> day,
>>>>>> but hopefully you guys agree that it is a good start towards a
>>>> consistent
>>>>>> feedback mechanism for the community to take advantage of the
>> different
>>>>>> distributed CI installations.
>>>>>> 
>>>>>> Please voice your feedback and concerns.  I am sure I have not though=
t
>>>> of
>>>>>> everything and we may still want to make fundamental changes to the
>>>>>> approach, but I think the concept is solid.
>>>>>> 
>>>>>> Cheers,
>>>>>> 
>>>>>> Will
>>>>>> 
>>>>> 
>>>> 
>> 
>> 
>> 
>> 
>> DISCLAIMER
>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>> This e-mail may contain privileged and confidential information which is
>> the property of Accelerite, a Persistent Systems business. It is intended
>> only for the use of the individual or entity to which it is addressed. If
>> you are not the intended recipient, you are not authorized to read, retai=
n,
>> copy, print, distribute or use this message. If you have received this
>> communication in error, please notify the sender and delete all copies of
>> this message. Accelerite, a Persistent Systems business does not accept a=
ny
>> liability for virus infected mails.
>> 


DISCLAIMER
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
This e-mail may contain privileged and confidential information which is the=
 property of Accelerite, a Persistent Systems business. It is intended only=
 for the use of the individual or entity to which it is addressed. If you ar=
e not the intended recipient, you are not authorized to read, retain, copy,=
 print, distribute or use this message. If you have received this communicat=
ion in error, please notify the sender and delete all copies of this message=
. Accelerite, a Persistent Systems business does not accept any liability fo=
r virus infected mails.