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

Clean Build wipes out repository

    XMLWordPrintable

Details

    Description

      When the Bazaar plugin is configured to "clean build" it wipes out the entire repository before every build, along with any artifacts created by previous builds.

      I am expecting it to wipe all files except for the repository itself. At least add a checkbox for this kind of functionality: cache the repository but remove any checked out / built files.

      Attachments

        Issue Links

          Activity

            zigarn Alexandre Garnier added a comment - github pull request : https://github.com/HudsonLabs/plugin-bazaar/pull/4

            Patch to correct this.
            Now, the update with clean option differs from initial branching by getting revision-id before cleaning the workspace and computing logs after branching.

            zigarn Alexandre Garnier added a comment - Patch to correct this. Now, the update with clean option differs from initial branching by getting revision-id before cleaning the workspace and computing logs after branching.

            Forget it, it's not the same thing.
            (But my idea is not bad, even if it doesn't solve this problem)

            zigarn Alexandre Garnier added a comment - Forget it, it's not the same thing. (But my idea is not bad, even if it doesn't solve this problem)

            The solution I use is to create a shared repository at jobs root folder.
            With this solution :

            • history is not in workspace and not wiped out
            • initial branching is faster if the branch has common history with an other job

            I do this by :
            $ cd $HUDSON_HOME/jobs/
            $ bzr init-repo .

            Then future jobs from Bazaar will use the shared repository.

            If you want to reconfigure existing jobs :
            $ cd $HUDSON_HOME/jobs/
            $ for job in $(\ls); do bzr reconfigure --use-shared $job; done

            I'll take a look for creating the shared repository at first branching (maybe then use checkouts and not branches).

            zigarn Alexandre Garnier added a comment - The solution I use is to create a shared repository at jobs root folder. With this solution : history is not in workspace and not wiped out initial branching is faster if the branch has common history with an other job I do this by : $ cd $HUDSON_HOME/jobs/ $ bzr init-repo . Then future jobs from Bazaar will use the shared repository. If you want to reconfigure existing jobs : $ cd $HUDSON_HOME/jobs/ $ for job in $(\ls); do bzr reconfigure --use-shared $job; done I'll take a look for creating the shared repository at first branching (maybe then use checkouts and not branches).
            paul_cannell paul_cannell added a comment -

            Yes, I've noticed this too.

            The most annoying part is how "clean build" wipes out the entire recent changes history.

            paul_cannell paul_cannell added a comment - Yes, I've noticed this too. The most annoying part is how "clean build" wipes out the entire recent changes history.

            People

              zigarn Alexandre Garnier
              cowwoc cowwoc
              Votes:
              2 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: