Return-Path: X-Original-To: apmail-cloudstack-dev-archive@www.apache.org Delivered-To: apmail-cloudstack-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 74DDD194B1 for ; Mon, 14 Mar 2016 04:25:56 +0000 (UTC) Received: (qmail 16299 invoked by uid 500); 14 Mar 2016 04:25:56 -0000 Delivered-To: apmail-cloudstack-dev-archive@cloudstack.apache.org Received: (qmail 16236 invoked by uid 500); 14 Mar 2016 04:25:56 -0000 Mailing-List: contact dev-help@cloudstack.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cloudstack.apache.org Delivered-To: mailing list dev@cloudstack.apache.org Received: (qmail 16224 invoked by uid 99); 14 Mar 2016 04:25:55 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 14 Mar 2016 04:25:55 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 36989C10CF for ; Mon, 14 Mar 2016 04:25:55 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.179 X-Spam-Level: * X-Spam-Status: No, score=1.179 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=2, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=disabled Authentication-Results: spamd1-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx2-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id 41bFFKe8sRhZ for ; Mon, 14 Mar 2016 04:25:54 +0000 (UTC) Received: from mail-ob0-f182.google.com (mail-ob0-f182.google.com [209.85.214.182]) by mx2-lw-eu.apache.org (ASF Mail Server at mx2-lw-eu.apache.org) with ESMTPS id 545625F39B for ; Mon, 14 Mar 2016 04:25:53 +0000 (UTC) Received: by mail-ob0-f182.google.com with SMTP id fp4so164623331obb.2 for ; Sun, 13 Mar 2016 21:25:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to; bh=TR95w4moXYwA/BxHBFGp7wOeOJdY4tJRw5FlPLUI3fU=; b=m0Oo9XJunpVGIzkhyabY3rKMzFWdXi3p1zZbw/0jstF+RsEr5O1AS5lMo7qsJlCbA8 DS/1JhK5ADRhKN4gVRBKjUskrNVWv7a8kkdtneUcJgDSPdPaaCqOyWfbBQ+IHa0prj0U DVT/dBd8/LrvcUTrMMjw/l22js0vzFU8Q/iWQAbk3k464zOopJhDojyZZGUZOa/RP5fc SRvVm2iBbf7nJ31V/SbO4ZMtotGIYYGhCeAjTvDFsyWnvND9Pvp7T3w+bM5i0qDeDlfh 9dUrSD9w16h8N0CaGgfv77hqcAB1xh7cm9e7q7QvxHECRwpDR+7hykuHKNQU0SWlMU03 2yOA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to; bh=TR95w4moXYwA/BxHBFGp7wOeOJdY4tJRw5FlPLUI3fU=; b=cfLTfk2A+5GX3JAqeFynqm3y8/J27R+ZFSqel9WQzPSOWtPGXmDRnwxvhaZcSQOXd9 edvt8ieeNUOVH+IVIIBISxXPzQGDCp1GzWQtPYiFPwHRxVPekw2EV7JB8GPcDbNlzMVu RSik+ZByqxwxGORf8gnSU+SUB5iLUQGWVVItSyNLYJvRf+RF/hCzW2UyZdXFMCRtiixT 2PwPfXKlVp6ZKWvtI7BD2VhjYHcp8pQASg01+Vm1O3ErPwN+7aTQIyUow8i7CFXzPNuJ aZ8nO2WnrQx6mx2BaxaB8Sz4sCbNLI9dgzEhq4KwLFwj5m4BcjRoBBzPS7lV1uAF/AOh g/Eg== X-Gm-Message-State: AD7BkJIKdEmJBT2MBWY1WZrpEa8YoOw5YpbnlA+F8HAi6v2yGzFF48lB2QqSeILpGKmhfIk5V44Q89LbzE5BjQ== MIME-Version: 1.0 X-Received: by 10.182.250.169 with SMTP id zd9mr12476845obc.59.1457929546291; Sun, 13 Mar 2016 21:25:46 -0700 (PDT) Received: by 10.202.197.136 with HTTP; Sun, 13 Mar 2016 21:25:46 -0700 (PDT) In-Reply-To: References: <56DA7EE2.4080305@gmail.com> Date: Mon, 14 Mar 2016 00:25:46 -0400 Message-ID: Subject: Re: [PROPOSAL] Minimum Viable CI Integration From: Will Stevens To: "dev@cloudstack.apache.org" Content-Type: multipart/alternative; boundary=089e0160c35cb6e327052dfaac8e --089e0160c35cb6e327052dfaac8e Content-Type: text/plain; charset=UTF-8 The latest version (0.2.0) of upr is now available... https://github.com/cloudops/upr All the details are in the README file of the repo, but the quick overview of the changes include: - Added the ability to comment on a pull request (by PR number or commit). - Implemented both S3 and Swift object storage backends for uploading files (tested with AWS S3, Cloudian (S3) and Swift). - Allow for automatic expiration of uploaded files to clean up the object store after a period of time (in both S3 and Swift). - Added the ability to override the default comment template with a local file (look at the current template for details). Let me know if you guys have questions, comments or feedback on that... Hopefully the apache infra guys will get back to me tomorrow so we can better assess how we need to move forward. Cheers, Will On Sun, Mar 13, 2016 at 7:11 PM, Will Stevens wrote: > Unfortunately this would only give us the ability to 'red light'/'green > light' pull requests via a distributed CI environments. The reason I > limited the request to this permission is because anything they give us > will be global to the entire apache org and this permission is restrictive > enough that we can't do damage elsewhere. There is a bit of history of them > denying all requests of this manner, so I wanted to focus on our minimum > viable use case, while limiting their liability, to improve our chances. > > You can follow the action here: > https://issues.apache.org/jira/browse/INFRA-11429 > > They have officially said no at this point, but I have asked them to > reconsider and asked them to provide suggestions for solving our problem. > > If they say no again, they will be doing so with the full knowledge that > the decision leaves us with our hands tied and we have exhausted our > official options through them. > > If we end up in this situation, we will have to get creative and I suspect > that will result in some activities moving outside the Apache repo. I have > not gone there (yet) since I feel that will need to be voted on in an > official thread of its own before we make a decision like that. > > Feedback and suggestions are very welcome. > > I am finalizing the 'comment' functionality in my tool 'upr' this weekend, > so that could give us some limited options. I will try to push a release > later tonight. It is all written and functional now, just need to clean up > the documentation and examples. > --089e0160c35cb6e327052dfaac8e--