Return-Path: Delivered-To: apmail-continuum-users-archive@www.apache.org Received: (qmail 7709 invoked from network); 2 Apr 2009 02:48:56 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 2 Apr 2009 02:48:56 -0000 Received: (qmail 24024 invoked by uid 500); 2 Apr 2009 02:48:55 -0000 Delivered-To: apmail-continuum-users-archive@continuum.apache.org Received: (qmail 23936 invoked by uid 500); 2 Apr 2009 02:48:55 -0000 Mailing-List: contact users-help@continuum.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@continuum.apache.org Delivered-To: mailing list users@continuum.apache.org Received: (qmail 23925 invoked by uid 99); 2 Apr 2009 02:48:55 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 02 Apr 2009 02:48:55 +0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of apache.maillist@gmail.com designates 209.85.132.247 as permitted sender) Received: from [209.85.132.247] (HELO an-out-0708.google.com) (209.85.132.247) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 02 Apr 2009 02:48:48 +0000 Received: by an-out-0708.google.com with SMTP id b2so238010ana.5 for ; Wed, 01 Apr 2009 19:48:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=QUPk0K84dy3ttLbzOcA6PUsZBE8VnimABri8v4ILG64=; b=dZRbj1+tKskteyqNcFu8kXwLzgNoOfDfClezozI1l35GPbZ4vlXddoejdFiofFHNc2 RaXReyjwqiypi7dUA2NKCpCWrZjHLuPFDR7VRCa2vjgQ4A1oSWgNqHBry/uyJidXH5e5 ++csm98DGv9t35xVbxH8NRGP1vkruuzVxNSJU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=xnbgPTXazkRBAgOXTvmvRQtGkKc+nSapEmho98rEfq5otbIuUXoBB+UrMLPxvCKKp3 wy+axKaDgx0KlAeMfMbrndpGSpGKqX7iuRnqwU9icv7WvjUL/sOagyugvIhY4Ji0uqC3 q4y4V71MQdGUy/fKfaxsgy+v8rUflXF81jsTA= MIME-Version: 1.0 Received: by 10.100.151.14 with SMTP id y14mr944872and.117.1238640507737; Wed, 01 Apr 2009 19:48:27 -0700 (PDT) In-Reply-To: References: <61ebb7260904011213j4dfa0743i5c649f4aaaf37487@mail.gmail.com> Date: Wed, 1 Apr 2009 19:48:27 -0700 Message-ID: <61ebb7260904011948p315fb323l4aeac5c80a005d87@mail.gmail.com> Subject: Re: Continuum Repository Purge Configurations, how does it work? From: "L. J." To: users@continuum.apache.org Content-Type: multipart/alternative; boundary=0016e644cf5c77e61a0466897700 X-Virus-Checked: Checked by ClamAV on apache.org --0016e644cf5c77e61a0466897700 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Thank you so much!! LJ On Wed, Apr 1, 2009 at 6:46 PM, Marica Tan wrote: > On Thu, Apr 2, 2009 at 3:13 AM, L. J. wrote: > > > Hi, > > > > We have multiple Continuum instances running on the same machine, each > one > > has the Repository Purge Configurations. > > 1. Does Repository Purge Configurations only purge SNAPSHOT? > > Yes > > > > > 2. Does each Continuum only purge the artifacts/projects it is hosting? > Or > > Continuum purges all the SNAPSHOT from local repo even it does not > contain > > the projects? > > > all snapshots in the repository that satisfy the conditions > > > > > 3. From 2, so do I set up Repository Purge Configurations for each > > Continuum > > instance or do I configure just one Repository Purge Configurations? > > > > you can configure just one for the same repository. > > > > > Thanks. > > > > LJ > > > --0016e644cf5c77e61a0466897700--