I propose to change the Database solution used in the integrity plugin from Derby to MapDB
      PROs:

      • MapDB is well known for it's performance and successfully used in several Jenkins plugins.
      • The original approach of "one database per job" would still be usable. This includes the handling of different credentials on Job-level
      • it is independent of the targeted Integrity-Server version

          [JENKINS-27217] Replace Derby DB by MapDB

          The current Derby DB implementation is a workaround and the ultimate goal is to completely eliminate it for core API calls. Hence I don't believe going to another DB worth the effort.

          Cletus D'Souza added a comment - The current Derby DB implementation is a workaround and the ultimate goal is to completely eliminate it for core API calls. Hence I don't believe going to another DB worth the effort.

            integrity_jenkins_plugin PTC ALM
            maschuru Matthias Rump
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: