How to pick up commit references from shared library repo directories

Added by Jon Povey over 10 years ago

Hi, we are rolling out Redmine + SVN, we have Redmine projects like
  • App1
  • App2
  • App3
And SVN structure like
  • App1 (/trunk /branches /tags)
  • App2 (/trunk /branches /tags)
  • App3 (/trunk /branches /tags)
  • Shared Libraries (/trunk /branches /tags)

The libraries are used by various different apps.
The Redmine projects are configured with their repository URLs as svn://host/repo/App1/ for example, if you have a bug reported on App1 and commit to Shared Libraries with a "refs" log messages referencing that bug, it isn't picked up by the App1 project as being a related commit.

I assume I could make all application repo paths in redmine point to svn://host/repo/ root, and each project would then see everything. That would make the repo browsing in Redmine a bit cluttered though, and you'd see log messages for revisions to unrelated application code.

Anyone got any ideas how I could configure or lay things out better?

Thanks,

Jon

Replies (3)

RE: How to pick up commit references from shared library repo directories - Added by Karl Heinz Marbaise over 10 years ago

Hi,
do you have an automated updating script to get the commits into Redmine or did you click on the repository menu entry and checked after that ...?
Kind regards
Karl Heinz Marbaise

RE: How to pick up commit references from shared library repo directories - Added by Jon Povey over 10 years ago

No cron job or commit hook. At the moment it's click on repository then go back and refresh ticket.

RE: How to pick up commit references from shared library repo directories - Added by Daniel Moore over 10 years ago

We have a similar situation:

    /trunk/productA
          /productB
          /sharedA
          /sharedB
          /sharedC

    /releases/productA-1-0/productA
                          /sharedA
                          /sharedB
                          /sharedC

             /productB-2-0/productB
                          /sharedC

All products live together in /trunk & each uses a different subset of the shared pieces.

Products are branched into /releases along with the code they share.

There's no single place to point the base of the project repo at that makes sense - the best
compromise is pointing at the root of the repo so that every project sees every change.

PS. Congrats on Redmine - easily the best bug system (+ so much more) I've seen & it's early days!

(1-3/3)