Re: [Trac] Re: One repository and two trac instances
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 28.04.2014 18:26, shath...@e-z.net wrote: > The trac subsystem complained > about a duplicate repository and disabled one. IMO this shouldn't be detected at all. So if you're running Trac 1.0 and could provide some more details about that setup, this should justify a ticket against the repository code management of Trac core. > When using trac-admin $ENV repository commands, I was able to > accomplish repository sharing across multiple trac environments. As I would expect. It might be an early hint to narrow the issue location down to some web-UI stuff rather than the main/db-facing "middleware" code? > I am still in the proof-of-concept stage of enterprise > deployment for Trac, Subversion, Apache2, and MS-Active > Directory authentication. Sounds like a reasonable Trac application, not too exotic. I guess, that there are already similar applications out there. > The ability to link repository updates to Trac tickets in > several environments would be useful, but not a show-stopper. > > My biggest concern regarding linking subversion commits > to Trac tickets would be how to enforce the recognition > of ticket linkage to only one of several repository > browsers. On the repository side (commit comments) TracLinks with InterTrac syntax will resolve with only suitable configured Trac out-of-the-box. I did already hint on the requirements for correct placement of commit messages to tickets of the referenced environment(s). > IMHO, only one trac environment should be > authoritative for repository maintenance, even if multiple > trac environments can serve as browsers. This reads a bit confusing. From Trac's side it is all management and linking, browser-only. Nothing that would neither allow nor require being authoritative in any obvious way. Any action beyond code examination has still to be done with native repository clients and tools. Hope, this clears it up a bit for you. Steffen Hoffmann -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Icedove - http://www.enigmail.net/ iEYEARECAAYFAlNei/QACgkQ31DJeiZFuHdyuwCgx2e9BzWXNu0vL8aLwpiXQZsZ Ok4An1J/hLX7mU32YAYGCYC0isZJ9OF0 =2r6+ -END PGP SIGNATURE- -- You received this message because you are subscribed to the Google Groups "Trac Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to trac-users+unsubscr...@googlegroups.com. To post to this group, send email to trac-users@googlegroups.com. Visit this group at http://groups.google.com/group/trac-users. For more options, visit https://groups.google.com/d/optout.
Re: [Trac] Re: One repository and two trac instances
FYI: I am also interested in the outcome of this discussion. When prototyping the ability to share a single subversion repository with two trac projects, the configuration was done initially with the trac.ini configuration files. The trac subsystem complained about a duplicate repository and disabled one. When using trac-admin $ENV repository commands, I was able to accomplish repository sharing across multiple trac environments. I am still in the proof-of-concept stage of enterprise deployment for Trac, Subversion, Apache2, and MS-Active Directory authentication. The ability to link repository updates to Trac tickets in several environments would be useful, but not a show-stopper. My biggest concern regarding linking subversion commits to Trac tickets would be how to enforce the recognition of ticket linkage to only one of several repository browsers. IMHO, only one trac environment should be authoritative for repository maintenance, even if multiple trac environments can serve as browsers. Sincerely, Steven J. Hathaway > Thanks Stefen, thanks Olemis > > On Friday, 25 April 2014 11:54:00 UTC+1, mimi wrote: >> >> Hi, >> >> I'd like to connect one svn repository with two track instances. >> >> I connected it smoothly (repo sync), but now I don't know how to link >> tickets from one trac instance and from second trac instance to the svn >> comment field. >> >> For example in first trac instance I have ticket no. 1 and in second >> trac >> instance I have ticket no. 4. >> >> When I do commit of my change into the repo I'd like to use links as >> usual >> #1 and #4. Of course when I use it and browse the source in first trac >> instance links #1 and #4 woks against first instance. And when I use it >> and >> browse the source in second trac instance links #1 and #4 works against >> the >> second one. >> >> Question: is there any extension to the #-type links which can point a >> particular ticket in the particular trac instance? Or have to put full >> url >> link? >> >> Thanks >> > > -- > You received this message because you are subscribed to the Google Groups > "Trac Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to trac-users+unsubscr...@googlegroups.com. > To post to this group, send email to trac-users@googlegroups.com. > Visit this group at http://groups.google.com/group/trac-users. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Trac Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to trac-users+unsubscr...@googlegroups.com. To post to this group, send email to trac-users@googlegroups.com. Visit this group at http://groups.google.com/group/trac-users. For more options, visit https://groups.google.com/d/optout.
[Trac] Re: One repository and two trac instances
Thanks Stefen, thanks Olemis On Friday, 25 April 2014 11:54:00 UTC+1, mimi wrote: > > Hi, > > I'd like to connect one svn repository with two track instances. > > I connected it smoothly (repo sync), but now I don't know how to link > tickets from one trac instance and from second trac instance to the svn > comment field. > > For example in first trac instance I have ticket no. 1 and in second trac > instance I have ticket no. 4. > > When I do commit of my change into the repo I'd like to use links as usual > #1 and #4. Of course when I use it and browse the source in first trac > instance links #1 and #4 woks against first instance. And when I use it and > browse the source in second trac instance links #1 and #4 works against the > second one. > > Question: is there any extension to the #-type links which can point a > particular ticket in the particular trac instance? Or have to put full url > link? > > Thanks > -- You received this message because you are subscribed to the Google Groups "Trac Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to trac-users+unsubscr...@googlegroups.com. To post to this group, send email to trac-users@googlegroups.com. Visit this group at http://groups.google.com/group/trac-users. For more options, visit https://groups.google.com/d/optout.
