Return-Path: Delivered-To: apmail-continuum-users-archive@www.apache.org Received: (qmail 83305 invoked from network); 2 Apr 2009 01:46:33 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 2 Apr 2009 01:46:33 -0000 Received: (qmail 87453 invoked by uid 500); 2 Apr 2009 01:46:32 -0000 Delivered-To: apmail-continuum-users-archive@continuum.apache.org Received: (qmail 87361 invoked by uid 500); 2 Apr 2009 01:46:31 -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 87351 invoked by uid 99); 2 Apr 2009 01:46:31 -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 01:46:31 +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 marica.tan@gmail.com designates 209.85.220.176 as permitted sender) Received: from [209.85.220.176] (HELO mail-fx0-f176.google.com) (209.85.220.176) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 02 Apr 2009 01:46:25 +0000 Received: by fxm24 with SMTP id 24so336504fxm.2 for ; Wed, 01 Apr 2009 18:46:03 -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=46+7XhFfgbaGfbTDWxyTN2vJhMW0Z0AEvYnkvhe5mpU=; b=CQzzop51Mzw6/Yib5uzkSrEvjqrWmWr6RHxRciAzyWeFduj3XAZlJJmdEg/72wZc7M 7ElPxjEdYEG0cPTFZ1+L+/WvLDeoZXwNeSRNkTHTrPbsUzJAoIvjTeMCKp9kDRDJP/ce J3y2HbF/qfypHbnKqXxH/9lc0aOVqnmmm2i48= 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=KjQ3OAJtwaS1nbCzKk7AyXv5nrF7yFpZ1lbFNdUBzWHQWfGAHIZClv/N+JPHWjOYVd Aq5p/JHyDPdcVAh0SU+4qdHfhifUcmQ0NdxVpb/FmJ/bYcnia3ee/jpLiO+YtgIbE1ee BHr4I8PHmtyvNT/NXhrjiiWWeWZyhOPqPmgPg= MIME-Version: 1.0 Received: by 10.204.61.137 with SMTP id t9mr3002418bkh.204.1238636763765; Wed, 01 Apr 2009 18:46:03 -0700 (PDT) In-Reply-To: <61ebb7260904011213j4dfa0743i5c649f4aaaf37487@mail.gmail.com> References: <61ebb7260904011213j4dfa0743i5c649f4aaaf37487@mail.gmail.com> Date: Thu, 2 Apr 2009 09:46:03 +0800 Message-ID: Subject: Re: Continuum Repository Purge Configurations, how does it work? From: Marica Tan To: users@continuum.apache.org Content-Type: multipart/alternative; boundary=0016e6dee96e4f5cad04668898ea X-Virus-Checked: Checked by ClamAV on apache.org --0016e6dee96e4f5cad04668898ea Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit 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 > --0016e6dee96e4f5cad04668898ea--