MIME-Version: 1.0
References: <5EC17E17.7070002@anastigmatix.net>
 <5ED270BA.9010001@anastigmatix.net>
 <5ED3D488.1010401@anastigmatix.net> <5ED474CA.3000106@anastigmatix.net>
 <CAASLQ4PfvmgKPp+aFf_r5RsBwigc+EC5Hm2CuzwJSTDCT64i-A@mail.gmail.com>
 <5ED4EA10.4030801@anastigmatix.net>
 <CAASLQ4Px21jyb2vJYSrjF5P0RqhA-G_DDWR9QHG68r+W+AqbxQ@mail.gmail.com>
 <CAASLQ4NYE-TW6hjbkSOuAY2Z4NM2cYzqSQ9ahO2LAUhdP9axeQ@mail.gmail.com>
 <5ED7E74B.9020800@anastigmatix.net>
 <CAASLQ4Od6-0=3+4ENKh1Z-Wcu5Wir-bwUn_ccO2UCmDhoR4vtQ@mail.gmail.com>
 <5EDA576E.2000204@anastigmatix.net>
 <CAASLQ4OzPwZB6GG_cXNW4WU4zpHa6wm8Q3WRWNv5pZpis+gf3w@mail.gmail.com>
 <5EDBA5D9.8090506@anastigmatix.net>
 <CAASLQ4P8e9XfUh17HFhYE4eMtq5-C4dpHQAX+hCsia-UFNAjtA@mail.gmail.com>
 <5EE7AE8C.2040201@anastigmatix.net>
 <CAASLQ4PoMTiTZUPxTR7VS8LLo9tosAMu-89T5ikWub7VbM+r4Q@mail.gmail.com>
 <5EEA6F85.9040009@anastigmatix.net> <5F063C86.3070301@anastigmatix.net>
 <5F47EB62.2060306@anastigmatix.net>
 <CAASLQ4N6_=u6nbi+0tD8SSCSO0oPjGLMib7n2c2u5=rSKE+MNw@mail.gmail.com>
 <5F4816A0.8020208@anastigmatix.net>
 <CAO5TtCuTyvyUDkY4iNGr-zUYJe6gy9+RmmO7Dm6QiNzL2p8WLA@mail.gmail.com>
In-Reply-To: 
 <CAO5TtCuTyvyUDkY4iNGr-zUYJe6gy9+RmmO7Dm6QiNzL2p8WLA@mail.gmail.com>
From: Kartik Ohri <kartikohri13@gmail.com>
Date: Sat, 29 Aug 2020 14:05:35 +0530
Message-ID: 
 <CAASLQ4NyFGd8J3iUpA3sCnkQ=4JccDjcHC=xrCemq9L4AdK+HQ@mail.gmail.com>
Subject: Re: Travis and AppVeyor continuous integration [Re:
 feature/master/ci]
To: thomas@tada.se
Cc: Chapman Flack <chap@anastigmatix.net>, pljava-dev@lists.postgresql.org
Content-Type: multipart/alternative; boundary="0000000000004ebf4a05ae000e25"
Precedence: bulk

--0000000000004ebf4a05ae000e25
Content-Type: text/plain; charset="UTF-8"

Hi!
On Sat, Aug 29, 2020 at 12:55 PM Thomas Hallgren <thomas@tada.se> wrote:

> Hi Chap,
>
> I'm somewhat reluctant to TravisCI due to its requirement for write
> permissions to *all* my repositories and associated data. Why would anyone
> grant an external CI service such permissions just to handle CI of *one* of
> my repositories, and why don't they offer a read-only alternative?
>

Travis recommends all repositories access but that can be easily restricted
to a single repository. Once, the application has been authorized. Github
will ask whether to install in a single repository or all.

Also, I checked which permissions the Travis app installed on my repo has.
The current Travis App has the write access to checks, commit statuses,
deployments, and repository hooks. The first three make sense but I am not
sure about the role of repository hooks. For what it's worth, AppVeyor
requires write access to only checks, commit statuses. However, in the
future I think we would like to deploy using Travis CI, Chap will be able
to provide more details in this case I believe. So, the only extra write
permission is for repository hooks which seems to be harmless but I may be
wrong.

Regards,
Kartik

--0000000000004ebf4a05ae000e25
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>Hi!</div><div dir=3D"ltr">On Sat, Aug 29, 2020 at 12:=
55 PM Thomas Hallgren &lt;<a href=3D"mailto:thomas@tada.se">thomas@tada.se<=
/a>&gt; wrote:<br></div><div class=3D"gmail_quote"><blockquote class=3D"gma=
il_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,2=
04,204);padding-left:1ex"><div dir=3D"ltr"><div style=3D"font-size:small;co=
lor:rgb(0,0,0)">Hi Chap,</div><div style=3D"font-size:small;color:rgb(0,0,0=
)"><br></div><div style=3D"font-size:small;color:rgb(0,0,0)">I&#39;m somewh=
at reluctant to TravisCI due to its requirement for write permissions to *a=
ll* my repositories and associated data. Why would anyone grant an external=
 CI service such permissions just to handle CI of *one* of my repositories,=
 and why don&#39;t they offer a read-only alternative? </div></div></blockq=
uote><div><br></div><div>Travis recommends all repositories access but that=
 can be easily restricted to a single repository. Once, the application has=
 been authorized. Github will ask whether to install in a single repository=
 or all.</div><div><br></div><div>Also, I checked which permissions the Tra=
vis app installed on my repo has. The current Travis App has the write acce=
ss to=C2=A0checks, commit statuses, deployments, and repository hooks. The =
first three make sense but I am not sure about the role of repository=C2=A0=
hooks. For what=C2=A0it&#39;s worth, AppVeyor requires write access to only=
=C2=A0checks, commit statuses. However, in the future I think we would like=
 to deploy using Travis CI, Chap will be able to provide more details in th=
is case I believe. So, the only extra write permission is for repository ho=
oks which seems to be harmless but I may be wrong.</div><div><br></div><div=
>Regards,</div><div>Kartik</div></div></div>

--0000000000004ebf4a05ae000e25--