[ 
https://issues.jenkins-ci.org/browse/JENKINS-13576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Kohsuke Kawaguchi resolved JENKINS-13576.
-----------------------------------------

    Resolution: Fixed

So I think essentially this boils down to JENKINS-6747, which just got fixed. 
Marking it as closed.
                
> Availability of "Use custom workspace" option for all job types (at same 
> location in job-configuration)
> -------------------------------------------------------------------------------------------------------
>
>                 Key: JENKINS-13576
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-13576
>             Project: Jenkins
>          Issue Type: Improvement
>          Components: core
>            Reporter: Deniz Bahadir
>              Labels: build, jenkins
>
> The option "Use custom workspace" is very useful (especially if several 
> projects need to access the same compiled code etc.).
> However, it is not available in all job types.
> I propose to make this a default-option for all job types available.
> Some solutions for similar issues addressing individual job types (e.g. 
> [Ivy|https://issues.jenkins-ci.org/browse/JENKINS-9464], 
> [Ivy/Maven|https://issues.jenkins-ci.org/browse/JENKINS-8848], 
> [Matrix|https://issues.jenkins-ci.org/browse/JENKINS-5077]) already exist, 
> however for other job types they do not. And the location of this option on 
> the job-configuration page is different.
> I tested the availability of the "Use custom workspace" option for the 
> following job types:
> * Freestyle
> ** Available at: "Advanced Project Options"-->"Advanced"
> * MultiJob
> ** NOT available!
> * Maven2/3
> ** Available at: "Build"-->"Advanced"
> * Ivy
> ** Available at: "Ivy Module Configuration"-->"Advanced"
> * Matrix
> ** Available at: "Advanced Project Options"-->"Advanced"
> * Montor External
> ** NOT available! (But maybe this makes sense!?)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to