Transitioning from BitBucket to GitLab

BitBucket allows small companies and developers to set up private repos free of charge with less than 10 users. The low price barrier is great but the BB UI is severely lacking in many respects. For example you can’t bulk edit issues which is a huge PITA if you’re dealing with a lot of tickets.

GitHub is a good alternative but not cheap if you have a large number of repositories. A better alternative for many may be GitLab, an open source platform which has all the bells and whistles of GitHub. For those who don’t wish to do the setup and hosting themselves you can pick up a VM running GitLab for just $5 / month.

While importing your repos into GitLab is very easy (it has a built in feature to do so) migrating your issues is somewhat more difficult. After looking around for a decent tool do to the job and finding nothing suitable I decided to write my own implementation. You can download it here.

 


2 thoughts on “Transitioning from BitBucket to GitLab

  1. This is exactly the kind of thing I’ve been looikng for, and I’m trying to get it working, unfortunately with no success yet.I’ve always run php and nginx inside a vm, so I forward ports in Virtualbox from the host OS to the guest and this works fine for my needs.I’ve basically copied my vh1 file to vh2 and changed the port and root path to the web app files. I can point my browser to localhost:3000 and view the vh1 app with no problems, but when trying to point my browser to localhost:3001 in another tab, the browser complains that it was unable to connect to the server. I’m guessing this precludes permissions problems, because when I get those, I at least see something getting parsed, but the browser tells me the file cannot be found.Also, in the terminal I try curl with both ports 3000 and 3001, and index.php seems to be parsed in both cases.My nginx vhost file contains an extra stanza that may be causing a hiccup(?):location ~ \.php$ {try_files $uri =404;fastcgi_split_path_info ^(.+\.php)(/.+)$;# NOTE: You should have “cgi.fix_pathinfo = 0;” in php.ini # With php5-cgi alone:fastcgi_pass 127.0.0.1:9000;# With php5-fpm:# fastcgi_pass unix:/var/run/php5-fpm.sock;fastcgi_index index.php;include fastcgi_params;}If you have any suggestions to get the extra vhosts running under that scenario, I’d be most grateful for your help

    • David

      Hey, I can’t solve your problem without more information. I’ll contact you directly ..

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes:

<a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code class="" title="" data-url=""> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong> <pre class="" title="" data-url=""> <span class="" title="" data-url="">