Archives for the tag “ svn ”

Stéphane Thibault >_

sthibault bookmarked a link:

The basic idea of story branching (sometimes referred to as “issue-driven development”) is that you create a development branch for each and every JIRA issue you implement. Bug fixes, user stories, spikes… they all get their own branch. Madness, you say! And I would agree with you if we were still using a centralized version control system like SVN. But branching in Git is very lightweight and merges don’t lock up the entire repository, making this crazy idea quite practical.

Stéphane Thibault >_

sthibault bookmarked a link:

If you read the previous section about using git svn, you can easily use those instructions to git svn clone a repository; then, stop using the Subversion server, push to a new Git server, and start using that. If you want the history, you can accomplish that as quickly as you can pull the data out of the Subversion server (which may take a while).

Stéphane Thibault >_

sthibault bookmarked a link:

From JIRA, you can use the JIRA DVCS Connector plugin to connect bitbucket or GitHub repositories to JIRA projects.  JIRA OnDemand includes the JIRA DVCS Connector plugin. For behind the firewall users, this is a system plugin that you can install. You can use the connector to connect public or private repositories. Once linked, the plugin identifies DVCS commit messages that reference a specific JIRA issue key and records the commit in JIRA. The information appears in the issue’s Activity and Commits section. The plugin records the commit message, the list of changed files, and provides links to view the change set.