Skip to content

news

utPLSQL is now open for sponsorship

In last months, we took steps to formalise utPLSQL and to give it a legal home under utPSLQL Development Labs Ltd. With this being almost complete, it is now time to open utPLSQL for sponsorship that will allow for sustained development of this great framework.

utPLSQL remains free to use and open source (Apache 2.0).


Incorporation of utPLSQL Development Labs Ltd

For many years, utPLSQL has been built and maintained through the contributions of dedicated and passionate engineers from the community.

To provide a sustainable legal structure for the project, utPLSQL is now under the legal custody of utPLSQL Development Labs Ltd.


Next chapter for utPLSQL

Looking back

utPLSQL v3 has come a long way since it was first released in 2017. It has already been over 10 years since the first discussions about starting the project began. However, development slowed after 2019, and by 2024 the project had become inactive. Life took me in a different direction for a few years, and the after-hours project understandably took a back seat.

Oracle 19c DB added to our CI/CD process

We take all the possible effort to assure utPLSQL can be tested against t all supported Oracle database versions.

Today, our automation got enriched with Oracle 19c database testing.

Pavel Kaplya has prepared a new small Docker Image for Oracle 19c.

Note:

You can take advantage of our efforts and build your own small Docker images (non-PDB) using our docker-scripts.

Continuous testing of utPLSQL

utPLSQL is now getting tested against five database versions: - Oracle 11g XE - Oracle 12c R1 - Oracle 12c R2 - Oracle 18c - Oracle 19c

You can see our build process & test results on travis-ci.org/utPLSQL

All of our deliverable projects use set of tools that are free to sue for Open-Source: - static code analysis using sonarcloud - publishing code coverage using coveralls - deploying java-api artifacts to packagecloud - deploying utPLSQL-cli artifacts to bintray - maven plugin publishing into maven repository

All of our builds must pass quality gates (code quality/tests/code coverage) before we approve and merge pull requests.