Description of problem: Use of hooks can be very useful for replicate changes to external repositories (ie. a central repository) Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Adding a bit of background information. Larger enterprises usually have policies around source code management and versioning. These kind of companies usually have a corporate standard SCM environment, managed by a dedicated team, which usually is also responsible for centralized builds, configuration and release and deployment management. Therefore, these enterprises would like a single 'source of truth' and manage BRMS and BPMSuite artifacts in their corporate standard SCM. To facilitate this, the idea is that the BRMS / BPMSuite Workbench clones an existing repository from the central Git SCM. Second, every change saved in the BRMS / BPMSuite workbench needs to be pushed to origin. Being able to use, for example, a Git post-commit hook would allow us automatically push every change to origin via a post-commit script, without manual intervention.
JGit is in process to add hook support, but still under dev. Maybe it's going to be available for 6.1.1
JGit 3.7 has something on Hooks now, I'll have a try on it soon. Some references: https://bugs.eclipse.org/bugs/show_bug.cgi?id=299315 https://git.eclipse.org/r/#/c/35476/
JGit 3.7 initial impl has limitations, but at least post-commit is supported: https://github.com/uberfire/uberfire/pull/110 (for windows it will need cygwin)
https://github.com/uberfire/uberfire/commit/e07ced2ae2865c6e628f3a4a5b83aa525350c61d
Feature requests are being tracked outside of Red Hat Bugzilla.