Quantcast
Channel: Zimbra Forums
Viewing all articles
Browse latest Browse all 1268

Installation and Upgrade • Re: Maldua's Zimbra 10 FOSS Build system

$
0
0
Thanks for the suggestions and I will investigate.

One thing I noticed on my builds that failed had to do with build.pl --build-release-no=${ZM_BUILD_RELEASE_NO} ... They have checking on this field so that 10.0.7 will work but 8.8.15.P1 will fail as a regex will catch that it's not 3 dot separated numbers. I ran into this with some building of versions when I attempted to do more here. For example, I ended up using the patch number with release 10.0.0 and specifying 10.0.7 which worked but 10.0.0.7 or 9.0.0.P35 would fail and there was no solution for 8.8.15 using that scheme.

They appear to be using: .circleci/misc/glean_version.pl to validity check release numbers if I understood what I was seeing in the zm-build directory.

Do you have a suggestion on standardizing the release no for these FOSS builds so everyone is on the same page and it looks somewhat similar to what NETWORK customers see?
Here is an example:

Code:

% zmcontrol -v% Release 10.0.7_GA_1000.RHEL8_64_20240301161421 RHEL8_64 FOSS edition.
where as my NETWORK version is:

Code:

% zmcontrol -vRelease 9.0.0_GA_3954.RHEL8_64_20200629045300 RHEL8_64 NETWORK edition, Patch 9.0.0_P39.
Maybe it doesn't matter and we use the 3rd digit unless they throw a more complex versioning scheme as they have historically done with their releases.

Jim

Statistics: Posted by JDunphy — Fri Mar 15, 2024 1:54 pm



Viewing all articles
Browse latest Browse all 1268

Trending Articles