Attention Lab developers: Developer Portal moved to Bitbucket!

From Virtual Labs Community
Jump to: navigation, search

- by VLEAD team

As yet another major step of adopting open and standard technologies for creating, integrating and publishing the Virtual Labs, VLEAD has migrated its Bazaar/SVN/Git version control services from IIIT-Hyderabad’s Developer Portal to Atlassian’s Bitbucket – a well known public domain service provider.

attlassian One of the attractive features of Bitbucket is that it offers free services to all Research and Academic institutions, and it uses the popular Git version control system. It also has a provision to keep the repositories either private or public, as per users need.

As a first step in this inclusive move to the modern version-control system, VLEAD has transferred the source code of all the labs (nearly 150) to Bitbucket. VLEAD engineers undertook this massive migration of labs by designing python automated scripts.

The repositories are made ‘private’, so that it will be available to only those (essentially the Lab Developers) who have login access to the repository. Lab developers need to register themselves at Bitbucket and sign up to view and manage their respective labs. (VLEAD has already communicated the repository details to all the Lab developers. The developers are expected to accept the invitation which will give them access to their respective repositories.)

The next step, therefore requires participation by the Lab Developers. Developers are expected to follow these steps:

  1. They need to sign up for a Bitbucket account with the same e-mail address which they use at Developer Portal. By doing so, their Bitbucket accounts will be identified as a Lab Developer’s account. On signing-up they should be able to view their repositories.
  2. If Lab developers are not familiar with Git version control system, they would be required to get acquainted with its few basic commands. Moving from Subversion or Bazaar to Git is pretty easy. There are many good resources on the web which explains Git clearly. One good tutorial is available at

    In our opinion, the following seven Git commands are adequate to effectively start using the new services:
    • git clone,
    • git add,
    • git commit,
    • git push,
    • git pull,
    • git log,
    • git status
  3. Lab Developers can start using Bitbucket for their lab’s version control needs. They could also use issue-tracking and wiki facilities accompanying the repository. (Note that every repository will have access to its own issue tracking and wiki facilities.)

This entry was posted in Uncategorized on March 7, 2014 by Jayashree Prasad.

Post navigation

Architecture of the Virtual Labs Hosting Ecosystem