Bug 1066962 – Add support for git hooks

Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.

Bug 1066962 - Add support for git hooks

Summary:	Add support for git hooks

Status:	VERIFIED

Aliases:	None

Product:	JBoss BRMS Platform 6
Classification:	Retired
Component:	Business Central (Show other bugs)
Sub Component:
Version:	6.0.0
Hardware:	Unspecified Unspecified

Priority	medium Severity unspecified
Target Milestone:	DR1
Target Release:	6.2.0
Assigned To:	Alexandre Porcelli
QA Contact:	Jiri Locker
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2014-02-19 06:48 EST by Alexandre Porcelli
Modified:	2015-11-03 06:21 EST (History)
CC List:	11 users (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:
Type:	Feature Request
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
JBoss Issue Tracker	PRODMGT-1251	Major	Pending Product Management Triage	Add support for git hooks	2018-08-16 20:28 EDT

Groups: None (edit)

Description Alexandre Porcelli 2014-02-19 06:48:05 EST

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 07:21:36 EST

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 06:52:39 EST

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 12:14:39 EDT

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 16:58:53 EDT

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 7 Alexandre Porcelli 2015-05-20 10:45:10 EDT

https://github.com/uberfire/uberfire/commit/e07ced2ae2865c6e628f3a4a5b83aa525350c61d

Comment 8 Lukáš Petrovický 2015-09-09 03:07:20 EDT

Feature requests are being tracked outside of Red Hat Bugzilla.

Note You need to log in before you can comment on or make changes to this bug.