#155 Bazaar Version Control Integration - Ruby on Rails

Type	To find
responsible:me	tickets assigned to you
tagged:"@high"	tickets tagged @high
milestone:next	tickets in the upcoming milestone
state:invalid	tickets with the state invalid
created:"last week"	tickets created last week
sort:id	tickets sorted by id (creation time)
Combine keywords for powerful searching.
Use advanced searching »

#155 √ incomplete

Bazaar Version Control Integration

Reported by Daniel Schierbeck | May 9th, 2008 @ 12:01 PM

Bazaar is a version control system used by many open source software projects; the Ubuntu project uses it for all its components.

Rails should support Bazaar just like it supports Subversion and Git.

Comments and changes to this ticket

Daniel Schierbeck May 9th, 2008 @ 12:06 PM
A very basic initial implementation can be found at .
Currently, you have to do
```
bzr init myproject

cd myproject

rails . --bzr
```
I need to hook into the application generator, doing a bzr init before anything is added. Furthermore, in the "add file" generator, I need to know the name of the project's root directory, i.e. /path/to/myproject, so I can do bzr add filename /path/to/myproject, because otherwise the user has to be in the project root directory.
Daniel Schierbeck May 9th, 2008 @ 12:07 PM
Hmm, the URL got stripped. It can be found at git://github.com/dasch/rails.git
Daniel Schierbeck May 9th, 2008 @ 01:14 PM
This is a working patch, requiring you to initialize the branch beforehand, and run rails . --bzr in the branch directory itself.
It also sets up an ignore list for Bazaar to use.
- rails-bzr.patch 3.6 KB
DHH May 11th, 2008 @ 07:23 PM
- → State changed from “new” to “incomplete”
I don't think we should ship with Bazaar support in the core necessarily. I'd rather if you could change the core such that adding additional SCM modules through plugins could be trivial. A plugin system like the one we have for template languages. That'd be really nice.
Daniel Schierbeck May 14th, 2008 @ 09:37 AM
That sounds reasonable, I'll have a look at it when I find the time.

Please Login or create a free account to add a new comment.

You can update this ticket by sending an email to from your email client. (help)

Create your profile

Help contribute to this project by taking a few moments to create your personal profile. Create your profile »

Source available from github

The Git repository resides at http://github.com/rails

Check out the current development trunk (Edge Rails) with:

git clone git://github.com/rails/rails.git

Creating or reviewing a patch

See the contributor guide.

Creating a feature request

Please don't. If you want a new feature in Rails, you'll have to pull up your sleeves and get busy yourself. Or convince someone else to do it. See the contributor guide on how to get going. But posting them here is just going to lead to ticket root.

Creating a bug report

When creating a bug report, be sure to include as much relevant information as possible. Post the code sample that causes the problem. Preferably, alter the unit tests and show through either changed or added tests how the expected behavior is not occuring.

Security vulnerabilities should be reported via an email to security@rubyonrails.org, do not use trac for reporting security vulnerabilities. All content in trac is publicly available as soon as it is posted.

Then don't get your hopes up. Unless you have a "Code Red, Mission Critical, The World is Coming to an End" kinda bug, you're creating this ticket in the hope that others with the same problem will be able to collaborate with you on solving it. Do not expect that the ticket automatically will see any activity or that others will jump to fix it. Creating a ticket like this is mostly to help yourself start on the path of fixing the problem and for others to sign on to with a "I'm having this problem too".