You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Several improvements to LibraryTesting needed: network SQLDB and docker images to run the tests #295
Support network based SQL database (postgresql) to be able to distribute the jobs much better on several computers without the fear of overriding sqlite3 files. Currently we copy locally the sqlite3 file then run the testing, then push back the results. If two computers run the same job they will override each other depending on which one finishes first / last. We should have a way to signal in the database which library we are testing against which OMC version and do not run the same from another computer, just skip it.
Use docker images for the Jenkins LibraryTesting so is easier to maintain
Activity
Add a sqlite3 to PostgreSQL migration and document the database
Let the testing use a shared PostgreSQL database instead of sqlite3 f…
sqlite3 to postgresql - migration (#296)
Make the configuration hash the same on every machine (#303)
Record the node a container is running on, not the container id (#322)
Run the library testing on a pull request (#307) (#324)
Run every library testing job in one docker image (#295) (#335)
adrpo commentedon Aug 27, 2026
Done!