Minimize the delay for new database versions

MongoDB Percona Server for MongoDB
1

At OpenEverest, we received a feature request to provide upstream faster by automating image pipeline for Percona Server for MongoDB as soon as the newer version of MongoDB is released. This was requested to have the security patch available quickly. You may see the detail here MongoDB make newer version automated available. · Issue #1752 · openeverest/openeverest · GitHub. Could you provide such experimental and untested build for purpose of allowing the community to use and test with associated risks?

I suggest a more “upstream-first” approach to keep Percona and Everest secure and up-to-date:

Automate the Image Pipeline: Implement automated builds in the percona/percona-server-mongodb repo that trigger as soon as a new MongoDB version is published.

Registry-Based Versioning: Change Everest’s logic to fetch available versions directly from the container registry tag list, rather than relying on a hardcoded list of tested versions.

“Experimental/Untested” Tags: To manage risk, these automated builds could be marked as “Untested” or “Experimental” in the Everest UI.

2

Hi @chilagrow - welcome to our community!

We’re very happy you’re working on the OpenEverest project!

I understand the concern you described. Currently, we’re not building nightly builds (or any pre-GA builds). However, we try to minimize the time between the upstream release time and Percona Server for MongoDB release time to as low as possible, while keeping an eye on performance, quality, and security. We’re also working on optimizing the source code merging process to make it more efficient and enable us to take a more streamlined approach to releasing faster.

I’ll place your enhancement request to our roadmap’s backlog. Thanks! I’ll update this thread here, when we know more about it.

1 Like