It probably makes sense to build all RPMs for CS8, even though we will not deploy them in production. It will help us to detect any code that may be broken by the next Linux version.
Designs
Child items
...
Show closed items
Linked items
0
Link issues together to show that they're related or that one is blocking others.
Learn more.
Looks like we should also upgrade Oracle instant client version: we currently rely on oracle-instantclient19.3-* but our public repository contains only versions >= 19.9.
I manage to compile only the CTA package: cta-cli. I've done it in another repository in https://gitlab.cern.ch/jcamarer/cta-centos8s , because I had to modify several files, and I thought it would make dirtier the CTA repository.
For the CI workflow we could use a multi-project pipeline to trigger the cat-centos8s project when we tag CTA.
The reason why I couldn't compile the full CTA project for Centos8S is the ABI. Libraries we can find in the Centos8S repos are compiled with the new gcc ABI. And if we use another library that is not compiled with this ABI (like oracle-instant-client 19), the project won't compile.
I would propose to update oracle-instant-client to the newest version. Or modify CTA to be able to compile without oracle-instant-client, but CTA for centos8S would loose any kind of communication with oracle databases.
I would go further and start to look into centos9 based builds. It's very likely, that many sites will skip centos9 and start to use centos9 (or it's clones) in the production.