-
Improvement
-
Resolution: Unresolved
-
Minor
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
Assignee | Original: Cletus D'Souza [ cdsouza ] | New: PTC ALM [ integrity_jenkins_plugin ] |
Workflow | Original: JNJira [ 161417 ] | New: JNJira + In-Review [ 180691 ] |
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.