| From: | Kartik Ohri <kartikohri13(at)gmail(dot)com> |
|---|---|
| To: | Chapman Flack <chap(at)anastigmatix(dot)net> |
| Cc: | pljava-dev(at)lists(dot)postgresql(dot)org |
| Subject: | Re: PL/Java new build plugin |
| Date: | 2020-07-14 17:40:59 |
| Message-ID: | CAASLQ4OYvTQL7ssG4=QyEqhaB71=AM-svBUYj3uRdWXWoQgBPw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pljava-dev |
>
> 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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Chapman Flack | 2020-07-14 17:56:26 | Re: PL/Java new build plugin |
| Previous Message | Kartik Ohri | 2020-07-14 17:36:43 | Re: PL/Java new build plugin |