Uploaded image for project: 'BxMS Documentation'
  1. BxMS Documentation
  2. BXMSDOC-8684

"Chapter 42.4. Configuring Git hooks as a system property for Business Central" is confusing

    XMLWordPrintable

Details

    • Bug
    • Resolution: Unresolved
    • Major
    • None
    • 7.13
    • Business Central

    Description

      Version 7.13 "Managing Red Hat Decision Manager and KIE Server settings" document has "42.4. Configuring Git hooks as a system property for Business Central".

      https://access.redhat.com/documentation/en-us/red_hat_process_automation_manager/7.13/html/managing_red_hat_process_automation_manager_and_kie_server_settings/managing-business-central-git-hooks-con#managing-business-central-configuring-git-hooks-system-property-proc-configuring-central

      Customer reports that in the first paragraph it states "If you do not have an existing Git repository project or if you want to apply post-commit Git hooks to a large number of project repositories you can specify a directory containing a hook file for the value of the org.uberfire.nio.git.hooks system property. This directory is copied to the Git repositories." In step 3 of the "Procedure" it states that "The post-commit Git hook is copied to all Business Central internal repositories and project repositories."

      This description makes customer confused. The template hook file only seems to be copied to new projects, not existing ones as implied by the documentation. To be more clear, only when a new repository is created, the hooks folder will be populated with the content of the folder configured before. If the repository is cloned, the folder won't be populated.

      Attachments

        Activity

          People

            dvoss@redhat.com David Voss
            rhn-support-omolinab Oscar Molina
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated: