[JIRA] (JENKINS-60314) Git knowledge base
Title: Message Title Thomas BASILIEN commented on JENKINS-60314 Re: Git knowledge base Thanks for your input, I will dig in the code to see what I can do ! Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203311.1574934344000.8585.1574936940382%40Atlassian.JIRA.
[JIRA] (JENKINS-60314) Git knowledge base
Title: Message Title Thomas BASILIEN updated an issue Jenkins / JENKINS-60314 Git knowledge base Change By: Thomas BASILIEN 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, the so it should work out of the box with the current jenkins database implementation. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to
[JIRA] (JENKINS-60314) Git knowledge base
Title: Message Title Thomas BASILIEN updated an issue Jenkins / JENKINS-60314 Git knowledge base Change By: Thomas BASILIEN 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, the it should work out of the box with the current jenkins database implementation. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to
[JIRA] (JENKINS-60314) Git knowledge base
Title: Message Title Thomas BASILIEN updated an issue Jenkins / JENKINS-60314 Git knowledge base Change By: Thomas BASILIEN 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) Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit
[JIRA] (JENKINS-60314) Git knowledge base
Title: Message Title Thomas BASILIEN created an issue Jenkins / JENKINS-60314 Git knowledge base Issue Type: Improvement Assignee: Tomas Westling Components: build-failure-analyzer-plugin Created: 2019-11-28 09:45 Priority: Minor Reporter: Thomas BASILIEN 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)
