Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1066962

Summary: Add support for git hooks
Product: [Retired] JBoss BRMS Platform 6 Reporter: Alexandre Porcelli <porcelli>
Component: Business CentralAssignee: Alexandre Porcelli <porcelli>
Status: CLOSED EOL QA Contact: Jiri Locker <jlocker>
Severity: unspecified Docs Contact:
Priority: medium    
Version: 6.0.0CC: abhumbe, agiertli, ahoffer, ddoyle, dvanbale, fspolti, jbride, kverlaen, lpetrovi, mbaluch
Target Milestone: DR1   
Target Release: 6.2.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-03-27 20:09:42 UTC Type: Feature Request
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Alexandre Porcelli 2014-02-19 11:48:05 UTC
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:

Comment 2 Duncan Doyle 2014-02-19 12:21:36 UTC
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.

Comment 4 Alexandre Porcelli 2014-12-30 11:52:39 UTC
JGit is in process to add hook support, but still under dev. Maybe it's going to be available for 6.1.1

Comment 5 Alexandre Porcelli 2015-04-13 16:14:39 UTC
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/

Comment 6 Alexandre Porcelli 2015-05-19 20:58:53 UTC
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)

Comment 8 Lukáš Petrovický 2015-09-09 07:07:20 UTC
Feature requests are being tracked outside of Red Hat Bugzilla.