I'd like jenkins to provide a document-oriented database to store such stuff, so that plugins can query for data objects (mapped by XStream ?) for build history. a mongoDB-like database to be 100% Java so it can be easily embedded in jenkins would be great
I don't know much about those options but what I've read on wikipedia, but document stores like Terrastore (http://code.google.com/p/terrastore/) or JackRabbit may be used for such use case. But, prior to talking about implementations, I also think some abstraction layer to (filesystem) data store is indeed the way to go, ad a first step 2012/9/11 Vojtech Juranek <[email protected]> > > Ideally a given AbstractBuild instance would hold very little in heap, so > > that you could scalably loads hundreds of them. > > > > Perhaps some > > kind of lightweight database, or RandomAccessFile / mapped ByteBuffer, > > could help this situation, if plugins were updated to keep per-build > > information in it? This would be moving toward some kind of abstraction > > over Jenkins instance storage, in place of the current getRootDir() > > free-for-all. > > +1 > load into the heap as few things as possible, rest refer by weak > references so > that memory can be freed if needed. > In long term add some abstraction layer which would allow to use some > database > or anything else and let the user choose if database + some cache should be > used or everything should be kept directly in the heap >
