MIME-Version: 1.0
From: Bear Giles <bgiles@coyotesong.com>
Date: Thu, 8 Jun 2023 14:39:34 -0600
Message-ID: 
 <CALBNtw4U927J7++-ZRzKvO2QZrFJfsmnp9GS3oCb_qyxkvrUaw@mail.gmail.com>
Subject: Announcing docker hub repos with auto-updating pgxnclient and pl/java
 pre-installed
To: pljava-dev@lists.postgresql.org
Content-Type: multipart/alternative; boundary="000000000000b2e73105fda44041"
Archived-At: 
 <https://www.postgresql.org/message-id/CALBNtw4U927J7%2B%2B-ZRzKvO2QZrFJfsmnp9GS3oCb_qyxkvrUaw%40mail.gmail.com>
Precedence: bulk

--000000000000b2e73105fda44041
Content-Type: text/plain; charset="UTF-8"

I won't finish with the CI/CD and 'readme' until tomorrow but I wanted to
announce my new docker hub repos with auto-updating pgxnclient and pl/java
preinstalled. I felt that giving you a bit of advance notice would make it
more likely I'll get feedback before I move onto a new task and have
totally forgotten why I was doing things that way. :-)


General Motivation

The motivation is the constant requests for help setting up a server ready
for use with pgxnclient, or pl/java in particular. Both PGXN and PL/Java
have a list of available docker images but those images are often very
out-of-date if they still exist at all.

Creating docker hub repos that are kept up-to-date via CI/CD (github
actions) won't solve everyone's problems... but it will solve a lot of
problems. This is especially true when I add an example of how to use these
repos, Docker, and TestContainers in order to greatly simplify testing the
*applications* that use these extensions.

(The docker images have pg-tap installed so you can easily run tests within
the docker container.)

The images are built using the official postgres releases on docker hub and
are intended as suitable drop-in replacements suitable for testing before
your code reaches your production database. There's some related work at
github.com/pgxn/pgxnclient but it looks like it's oriented around the
development of pgxn clients.


Personal Motivation

I want do resume working on some side-projects involving pl/java. I found
an easier version of these repos very useful since it made it trivial to
create fresh instances as I developed my code.

An application that's *using* an extension can use the appropriate docker
image. I'll be providing a TestContainer example that shows how the latest
version of the required jar(s). That's java-specific but easily extended to
other environments.

Someone who's *developing* an extension can use the *pgxnclient* image and
then use a similar approach to load both their extension and anything it
requires.


My github repo and CI/CD

This work is currently in the 'github-actions' branch of
beargiles/postgresql-pljava-docker.

The auto-update is handled via .github/workflows/main.yml. It will
periodically wake up (currently every Monday), get a list of tags for the
official postgres image, get a list of tags on my repos, and compare them.
Note: it only considers the base versions, e.g., '15.3', and only for major
releases of 12+. If there are any new tags the github action will build,
tag, and push the appropriate versions.

There's always an update of the major version, e.g., postgres-pljava:14.12
-> postgres-pljava:14.

There is also an update of 'latest' if appropriate.

Note: this *could* cause incorrect aliases if more than one minor version
is being added. I can't use a simple sort since the 'tags' are strings and
15.9 will appear to be more recent than 15.10. At this point I could
convert the tags to numbers and reliably sort those but I think it will be
enough to keep a short update cycle.


Testing

I'm using ansible and have put in the boilerplate for running molecule
tests on the newly built docker images. I haven't yet - but I'll probably
add a basic smoke test soon. Nothing fancy - just verifying that the docker
image can be successfully loaded.

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

<div dir=3D"ltr"><div class=3D"gmail_default" style=3D"font-family:tahoma,s=
ans-serif;color:rgb(0,0,0)"><p>I won&#39;t finish with the CI/CD and &#39;r=
eadme&#39; until tomorrow but I=20
wanted to announce my new docker hub repos with auto-updating pgxnclient
 and pl/java preinstalled. I felt that giving you a bit of advance=20
notice would make it more likely I&#39;ll get feedback before I move onto a=
=20
new task and have totally forgotten why I was doing things that way. :-)</p=
>
<p><br>
</p>
<p>General Motivation</p>
<p>The motivation is the constant requests for help setting up a server=20
ready for use with pgxnclient, or pl/java in particular. Both PGXN and=20
PL/Java have a list of available docker images but those images are=20
often very out-of-date if they still exist at all.</p>
<p>Creating docker hub repos that are kept up-to-date via CI/CD (github=20
actions) won&#39;t solve everyone&#39;s problems... but it will solve a lot=
 of=20
problems. This is especially true when I add an example of how to use=20
these repos, Docker, and TestContainers in order to greatly simplify=20
testing the <b>applications</b> that use these extensions.</p>
<p>(The docker images have pg-tap installed so you can easily run tests wit=
hin the docker container.)</p>
<p>The images are built using the official postgres releases on docker hub =
and are intended as suitable drop-in replacements suitable for testing befo=
re your code reaches your production database. There&#39;s some related wor=
k at <a href=3D"http://github.com/pgxn/pgxnclient">github.com/pgxn/pgxnclie=
nt</a> but it looks like it&#39;s oriented around the development of pgxn c=
lients.<br>
</p>
<p><br>
</p>
<p>Personal Motivation</p>
<p>I want do resume working on some side-projects involving pl/java. I=20
found an easier version of these repos very useful since it made it=20
trivial to create fresh instances as I developed my code.</p>
<p>An application that&#39;s <b>using</b> an extension can use the=20
appropriate docker image. I&#39;ll be providing a TestContainer example tha=
t
 shows how the latest version of the required jar(s). That&#39;s=20
java-specific but easily extended to other environments.<br>
</p>
<p>Someone who&#39;s <b>developing</b> an extension can use the <b>pgxnclie=
nt</b> image and then use a similar approach to load both their extension a=
nd anything it requires.<br>
</p>
<p><br>
</p>
<p>My github repo and CI/CD<br>
</p>
<p>This work is currently in the &#39;github-actions&#39; branch of beargil=
es/postgresql-pljava-docker.</p>
<p>The auto-update is handled via .github/workflows/main.yml. It will=20
periodically wake up (currently every Monday), get a list of tags for=20
the official postgres image, get a list of tags on my repos, and compare
 them. Note: it only considers the base versions, e.g., &#39;15.3&#39;, and=
 only
 for major releases of 12+. If there are any new tags the github action=20
will build, tag, and push the appropriate versions.</p>
<p>There&#39;s always an update of the major version, e.g., postgres-pljava=
:14.12 -&gt; postgres-pljava:14.</p>
<p>There is also an update of &#39;latest&#39; if appropriate.</p>
<p>Note: this <b>could</b> cause incorrect aliases if more than one=20
minor version is being added. I can&#39;t use a simple sort since the &#39;=
tags&#39;
 are strings and 15.9 will appear to be more recent than 15.10. At this=20
point I could convert the tags to numbers and reliably sort those but I=20
think it will be enough to keep a short update cycle.</p>
<p><br>
</p>
<p>Testing</p>
<p>I&#39;m using ansible and have put in the boilerplate for running=20
molecule tests on the newly built docker images. I haven&#39;t yet - but=20
I&#39;ll probably add a basic smoke test soon. Nothing fancy - just=20
verifying that the docker image can be successfully loaded.</p></div></div>

--000000000000b2e73105fda44041--