On Nov 23, 2011, at 4:01 AM, Hartmut Goebel wrote: > Hi! > > I'm one of the core developers of www.PyInstaller.org. Our main devel > platform is trac and we are quite happy with it. We are currently > investigating moving the repository (only the repository) to bitbucket or > github, so contributions are easier. > > Now if somebody checks in into the external repo (at bitbucket or github), we > want to see this in the e.g timeline. Also all changes should be available at > the track-instance, too. > > I've seen, github is providing some notification service and a plugin. > > Is there something similar for bitbucket? > Or are there other ways to achieve our goal? > > -- > > Schönen Gruß - Regards > Hartmut Goebel > Dipl.-Informatiker (univ.), CISSP, CSSLP > > Goebel Consult > Spezialist für IT-Sicherheit in komplexen Umgebungen > http://www.goebel-consult.de > > Monatliche Kolumne: http://www.cissp-gefluester.de/ > Goebel Consult ist Mitglied bei http://www.7-it.de > > -- > You received this message because you are subscribed to the Google Groups > "Trac Users" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/trac-users?hl=en. >
Hello! Just to clarify, this is my understanding thus far: You want to move your current internal SVN repository over to an external GIT repository? (I'm afraid I have _zero_ experience with bitbucket, so no help from me there). However, if my question is a 'Yes, thats what we want', then yes, it is possible. You will have to install the GIT plugin from Trac Hacks: http://trac-hacks.org/wiki/GitPlugin After which, you will need to perform the following on the local machine (the one in which Trac is installed): git clone http://some.external.site.com/git/project /some/local/data/base/location And, then continuously rebase the internal git data base at some interval from the some.external.site.com database, say once every two hours (don't want to spam that external site! be cautious of that…): 01 */2 * * * cd /some/local/data/base/location && /usr/bin/git rebase >/dev/null 2>&1 Every two hours Trac's Timeline will update based on the external github database. If you need Trac's Timeline updated more frequently, simply turn down the cron. You will never have instantaneous Timeline updates using this method of course. You should also be careful with updating your repository 'to' quickly. I don't want to know what happens when you do a git rebase when a previous git rebase is still busy downloading the hash changes. _________________ My real world example for 'Trac`ing' Libmesh from SourceForge: Local Trac machine: #>svn info https://libmesh.svn.sourceforge.net/svnroot/libmesh/trunk/libmesh (interested in the version only: 4983 as of the time of this email) #>mkdir -p /data/git/repos; cd /data/git/repos #>git svn clone -r 4950 https://libmesh.svn.sourceforge.net/svnroot/libmesh/trunk/libmesh (I really only want say… the last 30 or so checkins. No need to git all 4,983 revision changes!) #>crontab -e 01 */2 * * * cd /data/git/repos/libmesh && /usr/bin/git svn rebase >/dev/null 2>&1 (update my local GIT repo every 2 hours) I then setup Trac to use this local /data/git/libmesh/.git 'GIT' repository after installing the GIT plugin. I know these real-world instructions are using an external SVN repo instead of a GIT repo, but the concepts are exactly the same. Hope this helps! Jason -- You received this message because you are subscribed to the Google Groups "Trac Users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/trac-users?hl=en.
