Uploaded image for project: 'Bamboo Data Center'
  1. Bamboo Data Center
  2. BAM-8061

Really share instead of copy and paste

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Duplicate
    • None
    • Artifacts
    • None
    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      Don't take me wrong, Bamboo 3.0 is the closest to Hudson we've had so far (in terms of flexibility). I was almost able to duplicate a multi stage work from Hudson.

      My issue is the way things are "shared". First each job has a copy of the repository, there's no way to disabling checking out from the repository. In my case I have 5 jobs in my plan meaning I have 5 copies of the repository that needs to be updated. Meaning 5 times adding the time of updating the repository and 5 times the disk space consumption on disk.

      The second issue id that "shared" artifacts are not shared, just copied and pasted. I expected sharing to be exactly that, reuse the artifact. I think that all jobs within the same plan should be ran on the same place, using one repository copy instead of one per job, is not efficient in my opinion.

      The stage concept is great but the way it is implemented might not be the best. Stages/Jobs should be working on the same working directory not copies of them. Probably adding an option in the job to revert the repository would be equivalent to the clean repository copy each job uses now with the same resuts and less overhead.

              Unassigned Unassigned
              9b2a99b0c59d Javier A. Ortiz Bultron
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: