From easyant-dev-return-180-apmail-incubator-easyant-dev-archive=incubator.apache.org@incubator.apache.org Thu Jul 7 15:04:17 2011 Return-Path: X-Original-To: apmail-incubator-easyant-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-easyant-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id C5FF048D7 for ; Thu, 7 Jul 2011 15:04:17 +0000 (UTC) Received: (qmail 87060 invoked by uid 500); 7 Jul 2011 15:04:17 -0000 Delivered-To: apmail-incubator-easyant-dev-archive@incubator.apache.org Received: (qmail 87032 invoked by uid 500); 7 Jul 2011 15:04:17 -0000 Mailing-List: contact easyant-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: easyant-dev@incubator.apache.org Delivered-To: mailing list easyant-dev@incubator.apache.org Received: (qmail 87024 invoked by uid 99); 7 Jul 2011 15:04:17 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 07 Jul 2011 15:04:17 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of kpsiddharth@gmail.com designates 209.85.214.47 as permitted sender) Received: from [209.85.214.47] (HELO mail-bw0-f47.google.com) (209.85.214.47) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 07 Jul 2011 15:04:12 +0000 Received: by bwf20 with SMTP id 20so1093230bwf.6 for ; Thu, 07 Jul 2011 08:03:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=oIm9+PFnjKsvZoXJSnb6QjuFItlV8ZZ9k/dIAFe5OXg=; b=LgmhglCzhZ5KjxBQjISPglNQB2epzCpF180UrhZYYmN3m/NZRLu2rvPPNi4S/S1kXr qxDe+PhHcNfM5iBj8tuJxFX987xf+PWwn1SR/ljiz+31hw6HCWIBH6Zc0TPyvMYmZe3w xnGic3JVBWJcvxZwUlSeo25h0NHTcaevfjfxY= MIME-Version: 1.0 Received: by 10.204.14.212 with SMTP id h20mr771226bka.132.1310051030354; Thu, 07 Jul 2011 08:03:50 -0700 (PDT) Received: by 10.204.69.13 with HTTP; Thu, 7 Jul 2011 08:03:50 -0700 (PDT) In-Reply-To: References: <871uy619ip.fsf@v35516.1blu.de> <87y60ddnq5.fsf@v35516.1blu.de> Date: Thu, 7 Jul 2011 20:33:50 +0530 Message-ID: Subject: Re: [VOTE] Continunuous integration and repository management From: Siddhartha Purkayastha To: easyant-dev@incubator.apache.org Content-Type: multipart/alternative; boundary=000325555bca4d4a2a04a77c066c --000325555bca4d4a2a04a77c066c Content-Type: text/plain; charset=ISO-8859-1 Some additional thoughts: Single Repository will be less confusing to the user. Flip side of having a single repository will be that there will be nothing to prevent someone from injecting a dependency of the core on non-Apache compliant plug-ins inadvertently. Having a separate Apache repository will enforce this restriction. For CI, I think we should follow Apache conventions to the extent possible. In any case, non-apache compliant plug-ins such as checkstyle etc can not be considered a part of 'Apache EasyAnt' offerings. As I understand, there is also the need to maintain the sources for plug-ins that are *non-apache*. For such plug-ins, separate source repositories will be needed. These will be outside the purview of Apache. So it may also be possible that in the future, rights to develop on and build such plug-ins may vest on people of the larger community independent of the Apache EasyAnt dev team. As such, it may be helpful to have a clear separation between Apache and non-Apache sources, builds and resultant artifacts. Just to point out - if we are to use builds.apache.org, we will need EasyAnt installed on the build machines. I think that should not be a problem though. Thanks, Siddhartha On 6 July 2011 15:09, Jean-Louis Boudart wrote: > 2011/7/5 Stefan Bodewig > > > On 2011-07-04, Jean-Louis Boudart wrote: > > > > > We'll need to setup tons of jobs, one for core and then one for each > > plugins > > > as it could be released independently. I thought i was easier for all > to > > > have one place for both apache-compatible and non compatible stuff. > > > > Understood. > > > > > I feel confortable if we choose to use builds.apache.org for > > easyant-core > > > and core plugins, but in any case we need to have a second CI server > for > > > other plugins which could not be hosted @apache.org (such as > > checkstyle, > > > sonar etc...) > > > > Sounds good to me. > > > > Let's turn this in a more formal vote : > > Do we agree that we need one "repository" for both apache / non-apache > plugins ? see http://repository.easyant.org > [ ] YES > [ ] NO > > > Then for CI we have two options : > [ ] Option 1 : Have one CI server to build everything related to easyant > such as core, examples, plugins (including apache ones and non apache ones) > [ ] Option 2 : Have two distinct CI server. All Apache stuff (core + > examples + apache plugins) could use http://builds.apache.org. For the > rest > (plugins non compatible with apache license for example) could use > http://builds.easyant.org. > > Things to take in consideration : > Easyant is builded with easyant itself, all plugins required to build > easyant will be fetched from a repository (http://repository.easyant.org?) > this applies to both options. > > When we release easyant we will create an easyant distribution this > includes > ant + ivy + easyant-core + a set of common plugins for standard case. Like > for others apache deliverable the good host to make it accessible is > http://dist.apache.org. > If we choose Option 1 we will need to keep in mind that the easyant > distribution deliverable needs to be published on http://dist.apache.org. > > Which option do you prefer ? > > > -- > Jean Louis Boudart > Independent consultant > Apache EasyAnt commiter > http://incubator.apache.org/easyant/ > --000325555bca4d4a2a04a77c066c--