-
Improvement
-
Resolution: Unresolved
-
Minor
-
None
I saw that currently, we can save the elements on :
- Jenkins : filesystem
- Mongodb.
I would like to know your output about using git as the database ?
My pros for this are :
- We can add the git workflow to add / change / delete rules (with MR)
- We have the history of rules.
- The database can be readonly, if necessary (it my case, we have a lot constrain about service user with write rights)
- we have our Jenkins conf centralized on the same place (pipeline can get their conf from git)
- git manage files, so it should work out of the box with the current jenkins database implementation.
Hi Thomas,
I think it sounds like a good idea.
The information that is to be stored is suited well for git, since it is human-readable text.
The biggest pro for it would be the history, which sounds like a good reason to do it, in both of the current solutions, we only have a latest version of a failure cause.
And implementation-wise I guess it wouldn't be that hard to integrate with the existing git plugins.
It isn't something I have the time to look at, but feel free to hack away and create a pull request.