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

Clone workspace between jobs

    XMLWordPrintable

Details

    • Improvement
    • Status: Closed (View Workflow)
    • Critical
    • Resolution: Fixed
    • other
    • None
    • Platform: All, OS: All

    Description

      Seems that the usual way how jobs work on hudson is that there is one job for
      building a project and then if I want to have a subsequent job to run all unit
      tests, that job needs to download artifacts produced by that build job from
      Hudson. As a consequence, people usually add separate targets to their build
      scripts for running unit tests from hudson which download the build artifacts
      from the network.
      I think it would be nice if things could work the way how users would do it when
      running tests locally - i.e. use usual targets for building and then simply run
      a target for unit tests in the same workspace. This could be achieved by
      providing the subsequent jobs an exact snapshot of the workspace at the time
      when the parent job finished running.

      Attachments

        Issue Links

          Activity

            abayer Andrew Bayer added a comment -

            Not sure what you mean - matrix projects should be able to use the SCM part of it, at the very least. I'm not 100% sure how the publisher/archiver would work with a matrix project, though.

            abayer Andrew Bayer added a comment - Not sure what you mean - matrix projects should be able to use the SCM part of it, at the very least. I'm not 100% sure how the publisher/archiver would work with a matrix project, though.
            erwan_q erwan_q added a comment -

            This plugin is compatible with the matrix projects? If not it is possible?

            erwan_q erwan_q added a comment - This plugin is compatible with the matrix projects? If not it is possible?
            abayer Andrew Bayer added a comment -

            I've released the clone-workspace-scm plugin, which contains both a publisher for archiving workspaces and an SCM for, well, using those archived workspaces as SCM sources. It does need Hudson 1.350 or later - it'll blow up with earlier versions. I've got a wiki page up at http://wiki.jenkins-ci.org/display/JENKINS/Clone+Workspace+SCM+Plugin, but I need to do more work on the documentation. And as I mentioned before, the actual source is at GitHub (http://github.com/abayer/hudson-clone-workspace-scm-plugin) rather than the Hudson SVN repo.

            The plugin should show up in the Update Center within the next 6-12 hours.

            abayer Andrew Bayer added a comment - I've released the clone-workspace-scm plugin, which contains both a publisher for archiving workspaces and an SCM for, well, using those archived workspaces as SCM sources. It does need Hudson 1.350 or later - it'll blow up with earlier versions. I've got a wiki page up at http://wiki.jenkins-ci.org/display/JENKINS/Clone+Workspace+SCM+Plugin , but I need to do more work on the documentation. And as I mentioned before, the actual source is at GitHub ( http://github.com/abayer/hudson-clone-workspace-scm-plugin ) rather than the Hudson SVN repo. The plugin should show up in the Update Center within the next 6-12 hours.
            abayer Andrew Bayer added a comment -

            FYI, I've got this working (more or less - still a couple things to test and docs/tests to write) - it's up at http://github.com/abayer/hudson-clone-workspace-scm-plugin, though it'll need 1.350 to be released before I can release it.

            abayer Andrew Bayer added a comment - FYI, I've got this working (more or less - still a couple things to test and docs/tests to write) - it's up at http://github.com/abayer/hudson-clone-workspace-scm-plugin , though it'll need 1.350 to be released before I can release it.
            mmatula mmatula added a comment -

            @abayer - Yes, that looks good . Btw., re changelog - I guess it should just inherit the parent job's changelog.

            mmatula mmatula added a comment - @abayer - Yes, that looks good . Btw., re changelog - I guess it should just inherit the parent job's changelog.

            People

              abayer Andrew Bayer
              mmatula mmatula
              Votes:
              42 Vote for this issue
              Watchers:
              30 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: