From: | Vladimir Sitnikov <sitnikov(dot)vladimir(at)gmail(dot)com> |
---|---|
To: | List <pgsql-jdbc(at)postgresql(dot)org> |
Subject: | Release environment |
Date: | 2018-01-06 10:33:40 |
Message-ID: | CAB=Je-EMZqP51z8BUZteqjQGTWhvq+V2peH8xdtWNo-8RGqSbQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
Hi,
I used to use my machine for releasing pgjdbc, however it cannot serve that
purpose as I can no longer install Java 6.
I think Docker could serve the purpose of clean release environment.
If using Docker, we need to keep dockerfiles somewhere, and we need an
organization at Docker Hub (pgjdbc?) to store the images.
The following should work for us:
1) pgjdbc/maven-dependencies:x.y.z image that would store ".m2/repository"
cache, so the release won't require to download the same maven dependencies
again and again
2) pgjdbc/release-oraclejdk-8:x.y.z image to release Java8 build. It would
copy .m2 from the #1 image, and it would include mvn, gpg, git, etc. It
would fetch sources at release time.
3) Same for pgjdbc/release-oraclejdk-7, and other Java versions
There are open questions:
Q1) Where to store Dockerfiles? Should it be pgjdbc/release-env-docker?
Q2) Who creates and manages Docker Hub organization? Dave?
Q3) Where to get the backend from? It could be either port-forwarding or
something like docker-compose.
Any thoughts?
Vladimir
From | Date | Subject | |
---|---|---|---|
Next Message | pgjdbc CI | 2018-01-07 15:47:57 | [pgjdbc/pgjdbc] 59ed5e: chore: introduce release via Travis |
Previous Message | Michael Paquier | 2018-01-05 01:00:11 | Re: [JDBC] [HACKERS] Channel binding support for SCRAM-SHA-256 |