Redmine

+1 for this.

Could Redmine be modified to list all directories within the "root directory"?

If one of these directories doesn't contain the .bzr directory, Redmine will display the "The entry or revision was not found in the repository." error message (which currently shows when attempting to add a shared repository).

This would be very useful, especially for development with Bazaar using feature branching workflow.

I am willing to contribute to a bounty to make redmine browsing of Bazaar shared repositories work.

+1 for this also. Bazaar is gaining speed, just look at launchpad, and as of now there isn't an open source issue tracker supporting it's full feature set of workflows . I am also willing to contribute to a bounty not only for making shared repository browsing work within redmine, but a tighter integration with Bazaar in general.

+1 on this from me as well. Any updates?

+1

bzrtools has the branches command that lets you list branches in a location (`bzr branches`).
It will list branches regardless of there being a shared repository or not. The difficulty is more that depending on the number of folders, it could take quite a bit of time to search.
It probably wouldn't be a good idea to require the bzrtools plugin though, even though most who use bazaar probably have it installed. Will have a look at the source code for the command to see what it actually does. My guess is that it looks for .bzr folders, then runs bzr info to check and see if it's a branch or shared repository.

+1

I just found out about Redmine and it seems very interesting. I'm deploying it for testing for our little project and we need support for shared Bazaar repositories. I could work on this myself but as always I'm short on time and I've never even looked at ruby before.

Anyway, if someone begins developing this feature you can count me in for testing :)

+1

yeap, count me too on this...

somebody seems to have found some kind of workaround...

http://www.vxnick.com/2009/05/redmine-bazaar-repositories/

oops, I've just stumbled upon this...

http://www.redmine.org/wiki/redmine/RedmineRepositories#Bazaar-repository

silly me...

I don't see how the last 2 comments apply to this.

I too would like to be able to have the proper development tree structure available.

• bzr info will list 'shared repository: .'
• .bzr/repository exists.

If the path points to a shared repo, some file tree should be built.

• bzr info will list the root repository as 'shared repository'
• .bzr/branch exists.

• bzr info will list the root repository as 'shared repository' and the parent branch as 'parent branch'

As an example, let's examine the following repo:

$ mkdir /var/spool/bzr
$ bzr init-repo /var/spool/bzr
$ cd /var/spool/bzr
$ bzr info
Shared repository with trees (format: 2a)
Location:
  shared repository: .
$ ls -d .bzr/repository
.bzr/repository
$ bzr init fubar
$ cd fubar
$ bzr info
Repository tree (format: 2a)
Location:
  shared repository: /var/spool/bzr
  repository branch: .
$ ls -d .bzr/branch
.bzr/branch
$ bzr branch . foo
$ cd foo
$ bzr info
Repository tree (format: 2a)
Location:
  shared repository: /var/spool/bzr
  repository branch: .

Related branches:
  parent branch: /var/spool/bzr/fubar
$ ls -d .bzr/branch
.bzr/branch
$ cd /var/spool/bzr
$ bzr branch fubar bar
$ cd bar
$ bzr info
Repository tree (format: 2a)
Location:
  shared repository: /var/spool/bzr
  repository branch: .

Related branches:
  parent branch: /var/spool/bzr/fubar
$ ls -d .bzr/branch
.bzr/branch

In summary, if the path is a repo, scan the directory tree for directories containing .bzr/branch and run bzr info on those directories. Use that output to find out which branch is the parent and use that information to build the element tree.

I don't know how to do this in ruby, but hopefully someone can take this analysis and put something together.

+1

Any chance of this getting implemented ?

I think you need to create unit and functional test.

• source:tags/1.0.3/test/unit/repository_bazaar_test.rb
• source:tags/1.0.3/test/functional/repositories_bazaar_controller_test.rb

• https://github.com/edavis10/redmine/pull/15
• https://github.com/brentsowers1/redmine

Proceeding in my attempts to create a SCM module that does this cleanly, I am running into several issues. I am making my way through them (terribly slowly), but here's so far what I am looking for and lacking:

• What functions are expected to be in the SCM adapter class that inherits from Redmine::Scm::Adapters::AbstractAdapter? It would seem that at least entries, revisions, diff, cat, annotate are expected, but the various classes seem to disagree.

• What functions expected to appear in the SCM model class that inherits from the Repository model in app/models/repository.rb? Again, the different SCM models available do not seem to agree with each other so it's difficult for me to figure this out.

• It seems that Redmine expects a revision to be a property that persists throughout an entire repository. Am I right on that? If so, that is an impediment to implementation because revisions in Bazaar are per-branch properties (that is, given two branches A and B in shared repository R_A, revision 3 in branch A may differ from revision 3 in branch B and will thus have different underlying revision identifiers). In order to make this a bit better, there are full revision identifiers (which are somewhat similar to git's notion of revision identifiers, but not precisely), but I don't know how that would fit into the model that Redmine appears to expect. (It might help to know that Bazaar's shared-repository concept exists solely to save on storage costs: two identical revisions in two different branches will point to the same on-disk data. It is technically possible to have completely unrelated branches in a shared repository, but that's not the case in practice, because there is little point in doing so.)

• I am unclear on exactly how to build the information that the front-end requires. Reading through source code is not providing me the answers that I am seeking with any reasonable degree of efficiency, so some pointers on where to focus my attention would be greatly appreciated. Any information on assumptions or expectations of Redmine's repository management functionality would be helpful. Again, I am attempting to learn this from the sources, but I am finding it really, really difficult to read and truly comprehend the source code (mostly likely due to my unfamiliarity with Ruby, which I am attempting to learn as I go).

My biggest reason for working on this is to try to provide something that will be acceptable for integration into the mainline Redmine source and works in all situations that the bzr tool can handle itself, including branches and repositories that are not locally hosted on the system running Redmine. I don't know that I will be able to achieve that, though, so if someone else is working on this please don't stop doing so just because I'm attempting it.

I am stuck on this. From what I can tell, this cannot be done efficiently, if at all, because Bazaar uses a different model from what Redmine expects.

Bazaar has a much simpler model than other VCSes for shared repositories: they only hold the data that is shared between the branches. However, Redmine seems to make the assumption that it can do things such as specify a branch name in the revision field passed to the VCS, and the VCS will sort it all out. Same goes for tags.

Here are the issues that I have run into so far:

• It is not possible to efficiently get a list of all of the branches stored within a shared repository in Bazaar. The helper script that I have attached to this issue shows how it can best be done. However, this is not something that can be fixed in Redmine; the Bazaar VCS needs to cache the list of branches. Since branches cannot be added to the shared repository without Bazaar knowing about them (as far as I am aware), this should be a relatively easy bug to fix. Bazaar just needs to store the data in a catalog somewhere instead of deriving it every time it is needed.

• Since Redmine passes both branch names and tags as revision identifiers, ambiguities are possible. People identify a revision by speaking of a (branch, revno) pair, tags are the same way, (branch, tag). Both revnos and tags can exist in multiple branches and point to different things. IOW, it only makes sense to use a revno and a tag in concert with a branch. What I do not see is how to do this and solve for all possible use cases. For that to be possible, Redmine would have to treat the branch as its own attribute of a repository, and make revisions (and tags) both attributes of branches. That would, though, complicate things because as can be seen in the Subversion SCM plugin, Redmine does not attempt to use branches there since a Subversion repository layout does not adhere to a strict layout for branches or tags. In short, one-size-fits-all causes problems for one or the other.

• Because Redmine handles things the way it does, I do not see a means by which to identify a revision (passed in by the user) within the context of a branch (which they would be looking at). For that to work at all, Redmine would have to present to the SCM code a (branch, revno) pair (and the same goes for tags).

I am looking for a method by which this can be fixed, but it looks to me (admittedly, I am not an expert either in Ruby or the Redmine source code, so I could be way wrong here) that Redmine's concept of an SCM system has to be modified somewhat in order to make sense of things. This requires Redmine to store more data in its own database so that it is able to unambiguously pull up revisions from a Bazaar repository.

If Bazaar supported a repository-wide view of things, that would make things work just fine. However, all operations are performed on branches, not repositories, which is the biggest impediment. Until something changes, the current Bazaar plugin (which handles only a single branch) is the only way that things can work.

I would be welcome to suggestions or help. I'm in the IRC chat room, and am normally at my computer on and off throughout the day. This feature is critical to our adoption of the software, but I cannot proceed further with its implementation without at least some help and guidance.

Hi Eric,

is there a patch for Redmine 1.2.0?

Hi Eric, is there a patch for the latest 1.2.1 or 1.2.2 ?

Eric Seigne wrote:

Hi all,
here is a patch for redmine 1.2.2, i've just updated my redmine :)

Thx for your very quick reply. I will test this today.

Michael Trausch wrote:

I am stuck on this. From what I can tell, this cannot be done efficiently, if at all, because Bazaar uses a different model from what Redmine expects.

Why don't you just use the command bzr branches /path/to/shared/repo?

Does anyone by anychance have a patched version of the bitnami vm proposed in the download section? (or the turnkey one)

For the sake of future reference, and while it is not actual support for bazaar's features, latest Redmine versions support multiple repositories per project, which can alleviate the problem.

Lluís Vilanova wrote:

For the sake of future reference, and while it is not actual support for bazaar's features, latest Redmine versions support multiple repositories per project, which can alleviate the problem.

SO you suggest to add repository path to each branch ?

TridenT Job wrote:

SO you suggest to add repository path to each branch ?

Sorry, I'm not quite sure I understand what you mean. With current Redmine, what you can do is have a separate repository for each "branch". So accessing code through "http://code.server/bzr/project" is like accessing the main branch, while you can have the branch "feature1" stored in another repository of the same project ("http://code.server/bzr/project.feature1").

It's not the same, but I'm using it right now as a work-around.