Olav, The branches with task names are meant for bugs or features that take a long time, so that their reparation doesn't interfere with others' work and, for instances, breaks the trunk for a long time.
I normally don't create branches for bugs --only for new features that may take a while to implement. Rubén Pérez TELTEK Video Research www.teltek.es 2012/9/27 Olav Bringedal <[email protected]> > On 2012-09-26 21:32, Christopher Brooks wrote: > >> Hi, >> >> I've seen a bunch of +1's on list but no one has updated the wiki page >> of tasks in order to help make this a reality. +1 means you support >> the proposal both in spirit and in contribution, so please, if you >> really want this add your name next to a deliverable here: >> >> http://opencast.jira.com/wiki/**display/MH/Switching+to+Git<http://opencast.jira.com/wiki/display/MH/Switching+to+Git> >> >> And get to work on it; we won't be able to switch to git without these >> tasks finished (and potentially more). >> >> Chris >> > > I'm not the right person to solve this problem, but I'll try to explain > how we have done the jira-git integration at UiB. > > The svntogit script that we run on jenkins (https://github.com/uib/** > jenkins-svn2git <https://github.com/uib/jenkins-svn2git>) takes care of > both tags and branches automatically. (The jira branches looks a bit funny > in git though) > > Mapping from jira to git is done by cgit-commit-filter (relies on cgit, > but can probably be solved by other commit filters as well) which > transforms commit messages that has refs to a jira case to an url > > #!/usr/bin/perl -p >> >> s,(?:https://(?:jira\.uib\.no/**(?:jira/)?browse/)?(J[A-Z]+-\**d+),<a >> href="https://jira.uib.no/**browse/$1 <https://jira.uib.no/browse/$1> >> ">$1</a>,g; >> > > and from git to jira we use a jira-gitbot (attached) based on > http://confluence.atlassian.**com/display/JIRAEXT/JIRA+** > Command+Line+Interface<http://confluence.atlassian.com/display/JIRAEXT/JIRA+Command+Line+Interface> > > our repo: > https://github.com/uib/**matterhorn <https://github.com/uib/matterhorn> > > Last: About the branch mapping; why does each ticket need to be a branch, > isn’t that just making a big mess? I'm not very experienced with svn so > bare with me if this a silly question :) > -- > > Olav Bringedal > > Seksjon for integrasjon og applikasjonsutvikling > IT-Avdelingen UIB > > _______________________________________________ > Matterhorn mailing list > [email protected] > http://lists.opencastproject.org/mailman/listinfo/matterhorn > > > To unsubscribe please email > [email protected] > _______________________________________________ >
_______________________________________________ Matterhorn mailing list [email protected] http://lists.opencastproject.org/mailman/listinfo/matterhorn To unsubscribe please email [email protected] _______________________________________________
