Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-7952

Share Bazaar history in a shared repository to improve performances

    Details

    • Similar Issues:

      Description

      By creating a shared repository in 'jobs' folder, jobs from branches with common history will share it :

      • branching will be faster
      • less memory used

        Attachments

          Activity

          Hide
          laszlok Laszlo P added a comment -

          Even easier than using a shared repository:
          When clean is true, instead of workspace.deleteRecursive(), delete everything recursively except .bzr/. I mean, delete the entire working directory, but not the bzr info.

          Then do 'bzr revert --no-backup' to get a clean working tree and 'bzr pull --overwrite' to update the branch.

          This will save time and bandwidth compared to regular branching.

          Show
          laszlok Laszlo P added a comment - Even easier than using a shared repository: When clean is true, instead of workspace.deleteRecursive(), delete everything recursively except .bzr/. I mean, delete the entire working directory, but not the bzr info. Then do 'bzr revert --no-backup' to get a clean working tree and 'bzr pull --overwrite' to update the branch. This will save time and bandwidth compared to regular branching.
          Hide
          stewart Stewart Smith added a comment -

          There are some BZR bugs/problems with doing this with concurrent builds.

          Two bzr processes trying to create the same pack at the same time can conflict, leading to a not particularly happy state.

          I think it will be better to instead use stacked repositories to solve this problem.

          (I wish that shared repositories really did work... but it's not nearly reliable enough yet).

          Show
          stewart Stewart Smith added a comment - There are some BZR bugs/problems with doing this with concurrent builds. Two bzr processes trying to create the same pack at the same time can conflict, leading to a not particularly happy state. I think it will be better to instead use stacked repositories to solve this problem. (I wish that shared repositories really did work... but it's not nearly reliable enough yet).

            People

            • Assignee:
              sdirector Monty Taylor
              Reporter:
              zigarn Alexandre Garnier
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: