[JIRA] Commented: (HUDSON-682) Share workspace between jobs

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

[JIRA] Commented: (HUDSON-682) Share workspace between jobs

Hudson issues mailing list

    [ http://issues.hudson-ci.org/browse/HUDSON-682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=136303#action_136303 ]

peter_schuetze commented on HUDSON-682:
---------------------------------------

I don't see any use in having two jobs sharing a workspace but only one can write to this workspace. Than I can do that same stuff already with custom workspace and the locks-and-latches plugin or even simpler have one job do all the work.

For me the idea of creating two jobs, is that they can run at the same time. Which actually means that they have to different versions of the same workspace.

You also have to be careful with holding only the most recent workspace. Because what happens if job A is done and updates the most recent workspace while job is still working on the previous one? This must be supported.

> Share workspace between jobs
> ----------------------------
>
>                 Key: HUDSON-682
>                 URL: http://issues.hudson-ci.org/browse/HUDSON-682
>             Project: Hudson
>          Issue Type: Improvement
>          Components: other
>    Affects Versions: current
>         Environment: Platform: All, OS: All
>            Reporter: mmatula
>            Assignee: abayer
>            Priority: Critical
>
> 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.

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.hudson-ci.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]