Opened 18 years ago
Closed 15 years ago
#3368 closed enhancement (worksforme)
Repository subset support in commit hooks
Reported by: | Matthew Good | Owned by: | Christian Boos |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | version control | Version: | 0.9.6 |
Severity: | normal | Keywords: | post-commit hook multiproject multirepos |
Cc: | Branch: | ||
Release Notes: | |||
API Changes: | |||
Internal Changes: |
Description
One of the issues mentioned in #2789 was that the commit hook scripts don't handle the setup where you have one repository containing many projects. You can only have one commit script for the repository, so it needs to determine based on the path of the commit which projects it pertained to.
Attachments (0)
Change History (5)
comment:1 by , 18 years ago
Keywords: | post-commit hook multiple project added |
---|---|
Milestone: | → 2.0 |
comment:2 by , 16 years ago
Milestone: | 2.0 → 0.12 |
---|
comment:3 by , 16 years ago
Owner: | changed from | to
---|
comment:4 by , 16 years ago
Keywords: | multiproject multirepos added; multiple project removed |
---|
I think the new hook (trac-svn-hook) handles this situation correcly.
Let's imaging the following repository structure:
projA/{trunk,branches,tags}
projB/{trunk,branches,tags}
Now we have Trac envA using projA
as its scope and Trac envB using projB
as its scope.
By specifying a TRAC_ENV variable /path/to/envA:/path/to/envB
, both environments will be notified of new changesets and changesets "out of scope" will be ignored.
comment:5 by , 15 years ago
Milestone: | 0.12 |
---|---|
Resolution: | → worksforme |
Status: | new → closed |
The new post-commit hook in MultiRepos makes this possible. We should add an example.