Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-60314

Git knowledge base

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      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.

        Attachments

          Activity

          superbasil3 Thomas BASILIEN created issue -
          superbasil3 Thomas BASILIEN made changes -
          Field Original Value New Value
          Description 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)
          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)
          superbasil3 Thomas BASILIEN made changes -
          Description 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)
          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.
          superbasil3 Thomas BASILIEN made changes -
          Description 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.
          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.

            People

            Assignee:
            t_westling Tomas Westling
            Reporter:
            superbasil3 Thomas BASILIEN
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Dates

              Created:
              Updated: