Return-Path: X-Original-To: apmail-stratos-dev-archive@minotaur.apache.org Delivered-To: apmail-stratos-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 762BB1775E for ; Mon, 20 Oct 2014 06:25:57 +0000 (UTC) Received: (qmail 31031 invoked by uid 500); 20 Oct 2014 06:25:56 -0000 Delivered-To: apmail-stratos-dev-archive@stratos.apache.org Received: (qmail 30979 invoked by uid 500); 20 Oct 2014 06:25:55 -0000 Mailing-List: contact dev-help@stratos.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@stratos.apache.org Delivered-To: mailing list dev@stratos.apache.org Received: (qmail 30968 invoked by uid 99); 20 Oct 2014 06:25:55 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 20 Oct 2014 06:25:55 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of mariangela@wso2.com designates 209.85.214.182 as permitted sender) Received: from [209.85.214.182] (HELO mail-ob0-f182.google.com) (209.85.214.182) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 20 Oct 2014 06:25:29 +0000 Received: by mail-ob0-f182.google.com with SMTP id uy5so3332130obc.13 for ; Sun, 19 Oct 2014 23:25:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=wso2.com; s=google; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=m3BIAEixwxn+gbiFMl5e3s8TPm8AcsvCgQGz29mM9fs=; b=asRMiHWkqoFqjGGR/LIJstWxdERQikH0OCIdLkdKCKwQ/NbT6ekqE+E6+xk5I9W5Pk CXmml8FfBlHL/Iw6JGNuPmWJ1IO43+TDG9BaLCLZvVIdY30nqn3Ah5Gt2+QTewbxe7Zd 7XIzIJwha7n21XKuffTIw1ZYcIAjEK6EiqRMA= 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:from:date :message-id:subject:to:cc:content-type; bh=m3BIAEixwxn+gbiFMl5e3s8TPm8AcsvCgQGz29mM9fs=; b=aF1vqoxgUNbnLbTv4PQX5sYMUtEioQXsLj2U2a+3ZCL2VyYfrA5U4DZJL55WtaoPu1 WshG/yoPIu+s2Lf83v5fUOikp/waFajvRFZbFSHp5SC9dpHAjcUmXVwqwJk3pxdMzjzC MnWY6RfTIj/htGsTY1iLpwYgW6bzb2cm/zYpQL5n943a0m54l2PsJL5RNNF+ZXQKJMdk tUwrYupunXLLE7jPN/Y+e6WbNkXgvGZ2i25vh444D8LFslWxeti7mk+cWE+1YDjnsKn7 2BexBBD/C2troUGwdZXpWygDbxqulj+muc+MeBwWv2uFImxcr4c0u3GpdreeJ/agItNm +s3A== X-Gm-Message-State: ALoCoQmyVxAKcGzh+Hgp1GGUD5lvqyLtcIDqWWJBz+0si270K4fes50Uh3WwLvz5QK0w58jbpM7q X-Received: by 10.202.215.70 with SMTP id o67mr20370440oig.15.1413786328150; Sun, 19 Oct 2014 23:25:28 -0700 (PDT) MIME-Version: 1.0 Received: by 10.76.28.137 with HTTP; Sun, 19 Oct 2014 23:25:07 -0700 (PDT) In-Reply-To: References: From: Mariangela Hills Date: Mon, 20 Oct 2014 11:55:07 +0530 Message-ID: Subject: Re: Commits enabled payload parameter To: Akila Ravihansa Perera Cc: dev Content-Type: multipart/alternative; boundary=001a113d42dce0d0d10505d4c727 X-Virus-Checked: Checked by ClamAV on apache.org --001a113d42dce0d0d10505d4c727 Content-Type: text/plain; charset=UTF-8 Hi Akila, Page [1] discusses auto commit. While, [2] and [3] mention how it can be used. Please let me know whether any more information needs to be added to these pages. [1] https://cwiki.apache.org/confluence/display/STRATOS/4.0.0+Artifact+Distribution+Coordinator#id-4.0.0ArtifactDistributionCoordinator-AutoCommit [2] https://cwiki.apache.org/confluence/display/STRATOS/4.0.0+subscribe-cartridge [3] https://cwiki.apache.org/confluence/display/STRATOS/4.0.0+Subscribing+to+a+Cartridge Regards, Mariangela *--* Mariangela Hills Senior Technical Writer *WSO2, Inc.*lean.enterprise.middleware. m: +94 773 500185 w: http://wso2.com On Thu, May 8, 2014 at 8:01 AM, Akila Ravihansa Perera wrote: > Hi, > > Can someone explain the purpose of having "commits enabled" parameter > in the payload. Looks like the cartridge agent is periodically > checking the Git repo and pushing changes if this is enabled. But do > we need that in all types of cartridges (for eg - data cartridge)? > Besides we cannot set Repo URL or Commits enabled parameters for data > cartridges from the UI (Management console). IMO, this parameter > should be optional. > > Thanks > > PS - Would be nice to have a Wiki page to explain all payload parameters :) > > -- > Akila Ravihansa Perera > Software Engineer > WSO2 Inc. > http://wso2.com > > Phone: +94 77 64 154 38 > Blog: http://ravihansa3000.blogspot.com > --001a113d42dce0d0d10505d4c727 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi Akila,

Page [1] discusses auto commi= t.=C2=A0 While, [2] and [3] mention how it can be used. Please let me know = whether any more information needs to be added to these pages.



Regards,
Mariangela


--

Mariangela Hills
Senior Technical Wr= iter
=
= WSO2, Inc.
lean.enterprise.middleware.
=C2=A0


On Thu, May 8, 2014 at 8:01 AM, Akila Raviha= nsa Perera <ravihansa@wso2.com> wrote:
Hi,

Can someone explain the purpose of having "commits enabled" param= eter
in the payload. Looks like the cartridge agent is periodically
checking the Git repo and pushing changes if this is enabled. But do
we need that in all types of cartridges (for eg - data cartridge)?
Besides we cannot set Repo URL or Commits enabled parameters for data
cartridges from the UI (Management console). IMO, this parameter
should be optional.

Thanks

PS - Would be nice to have a Wiki page to explain all payload parameters :)=

--
Akila Ravihansa Perera
Software Engineer
WSO2 Inc.
http://wso2.com

Phone: +9= 4 77 64 154 38
Blog: http:= //ravihansa3000.blogspot.com

--001a113d42dce0d0d10505d4c727--