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

Shared workspace between jobs or different actions in the same job?



    • Improvement
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Duplicate
    • core
    • None
    • Platform: All, OS: All


      A common issue building projects is to have several actions done on the same

      Imagine you have a project A and you want to add a Subversion hook so you can
      compile and run tests every time you make a commit. Also you want to be able to
      generate a web site every night.

      This scenario could be interpreted as project A build with two build triggers, a
      default one to just compile and test and another one to have project's site
      generated, which is launched, i.e., everyday at 2a.m.

      Nowadays if you you want this feature done with Hudson it´s necessary to define
      two separated jobs, each one with its own copy of the project.

      If you have many different actions on the same project you have so many jobs in
      Hudson each one with its on workspace copy.

      Why not share this workspace?


        Issue Links


            pablomuniz pablomuniz created issue -
            kohsuke Kohsuke Kawaguchi made changes -
            Field Original Value New Value
            Resolution Duplicate [ 3 ]
            Status Open [ 1 ] Resolved [ 5 ]
            kohsuke Kohsuke Kawaguchi made changes -
            Link This issue duplicates JENKINS-682 [ JENKINS-682 ]
            abayer Andrew Bayer made changes -
            Status Resolved [ 5 ] Closed [ 6 ]
            ircbot Jenkins IRC Bot made changes -
            Component/s core [ 15593 ]
            Component/s www [ 15484 ]
            rtyler R. Tyler Croy made changes -
            Workflow JNJira [ 130471 ] JNJira + In-Review [ 199846 ]


              Unassigned Unassigned
              pablomuniz pablomuniz
              0 Vote for this issue
              0 Start watching this issue