MIME-Version: 1.0
References: 
 <CAASLQ4Mva7dAXiS_c9OLhV4VzNHF=XNKJosuS5gtZTB6b4TW1Q@mail.gmail.com>
 <CAASLQ4NOq2FcTvp1hB-kTnJZgxfRP=u20gfQT=tgpvBq+9Ac-w@mail.gmail.com>
 <CAASLQ4PwL2U6t0DYZK4KF9+2UZT56Npcga4xZWWfo04w2QZxCQ@mail.gmail.com>
 <5F04FA65.5000600@anastigmatix.net>
 <CAASLQ4PEe0_1dE-iOBv27fX1SUH0=ewDm=6w9chHLjWSAkeNgQ@mail.gmail.com>
 <5F071CFC.9090306@anastigmatix.net>
 <CAASLQ4MLFd6zhoh+sWWz+iu4d8+H2ML+y=kL990k7H=kk74pvA@mail.gmail.com>
 <5F072647.50301@anastigmatix.net>
 <CAASLQ4Ms0QGf-Qh966HrsoaWzwf1SYHZ0WmZHApQePbcyPejCQ@mail.gmail.com>
 <CAASLQ4NFHYH1pfGJtCZDfdcxf_ZzLA+X+ko86vpyRDKVYr489Q@mail.gmail.com>
 <5F0734AD.7060001@anastigmatix.net>
 <CAASLQ4PDcaAJ8fEwXXFW6XPakc7GCNVgPNGCxA8KYMzPDZw4+w@mail.gmail.com>
 <5F077926.2050806@anastigmatix.net>
 <CAASLQ4OuFQCiSMeypQtfRaAvj-4H-EAgszLwdAo6Tc1zS9B66g@mail.gmail.com>
 <5F07C2D5.5050904@anastigmatix.net>
 <CAASLQ4PSizkzBKyyfkp9ccJ1qDPLRLu6g2bo9cN-XuTzGQFGfQ@mail.gmail.com>
 <CAASLQ4P9zGxHda=HAGJ2eAa-oMmJtnPm=4a14mj4P-QpfFsYxg@mail.gmail.com>
 <5F0D35BA.30904@anastigmatix.net>
 <CAASLQ4NmornyOW8n-qyneLpDVPgV0Js=+=Eys6bw3Y-ZiVbVjA@mail.gmail.com>
In-Reply-To: 
 <CAASLQ4NmornyOW8n-qyneLpDVPgV0Js=+=Eys6bw3Y-ZiVbVjA@mail.gmail.com>
From: Kartik Ohri <kartikohri13@gmail.com>
Date: Tue, 14 Jul 2020 23:10:59 +0530
Message-ID: 
 <CAASLQ4OYvTQL7ssG4=QyEqhaB71=AM-svBUYj3uRdWXWoQgBPw@mail.gmail.com>
Subject: Re: PL/Java new build plugin
To: Chapman Flack <chap@anastigmatix.net>
Cc: pljava-dev@lists.postgresql.org
Content-Type: multipart/alternative; boundary="000000000000258a0705aa6a50ac"
Precedence: bulk

--000000000000258a0705aa6a50ac
Content-Type: text/plain; charset="UTF-8"

>
> Sure. Running a CI check is as easy as opening a PR against the master
> branch of my PL/Java fork. For this case,
> https://github.com/amCap1712/pljava/pull/4 . At the bottom, you can click
> details next to the CI provider to view detailed logs of each build. As of
> now, the Windows build will fail for Java 9, 10 (probably PG 9 as well) in
> any case so that can be ignored. I'll notify you once the build is done.
>

I just checked Appveyor CI builds for Windows (even those which work
properly) are failing. You can view the logs at
https://ci.appveyor.com/project/amCap1712/pljava/builds/34092481 .  Also,
you can push new commits to your branch and the CI will automatically start
a new against them. The link to the new build will be available on the PR
page.

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

<div dir=3D"ltr"><div class=3D"gmail_quote"><blockquote class=3D"gmail_quot=
e" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204)=
;padding-left:1ex"><div dir=3D"ltr"><div class=3D"gmail_quote"><div>Sure. R=
unning a CI check is as easy as opening a PR against the master branch of m=
y PL/Java fork. For this case,=C2=A0<a href=3D"https://github.com/amCap1712=
/pljava/pull/4" target=3D"_blank">https://github.com/amCap1712/pljava/pull/=
4</a>=C2=A0. At the bottom, you can click details next to the CI provider t=
o view detailed logs of each build. As of now, the Windows build will fail =
for Java 9, 10 (probably PG 9 as well) in any case so that can be ignored. =
I&#39;ll notify you once the build is done.</div></div></div></blockquote><=
div><br></div><div>I just checked Appveyor CI builds for Windows (even thos=
e which work properly) are failing. You can view the logs at=C2=A0<a href=
=3D"https://ci.appveyor.com/project/amCap1712/pljava/builds/34092481">https=
://ci.appveyor.com/project/amCap1712/pljava/builds/34092481</a>=C2=A0.=C2=
=A0=C2=A0Also, you can push new commits to your branch and the CI will auto=
matically start a new against them. The link to the new build will be avail=
able on the PR page.</div></div></div>

--000000000000258a0705aa6a50ac--