[
https://issues.jenkins-ci.org/browse/JENKINS-12889?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rob Petti updated JENKINS-12889:
--------------------------------
Component/s: core
(was: perforce)
Changing components to 'core', since this is unrelated to the perforce plugin.
> Jenkins "Workspace" presents "Run a build" even when Builds are Disabled
> ------------------------------------------------------------------------
>
> Key: JENKINS-12889
> URL: https://issues.jenkins-ci.org/browse/JENKINS-12889
> Project: Jenkins
> Issue Type: Improvement
> Components: core
> Affects Versions: current
> Environment: Jenkins: 1.451
> Perforce SCM Plugin: 1.3.8
> tomcat: 6.0.33-1.26
> Reporter: Colin Johnson
> Priority: Trivial
> Attachments: jenkins - Unable to Build because Build Disabled.txt
>
>
> Summary: Clicking "Run a build to have Jenkins create a workspace" is
> presented to user in Workspace, and clicking on link presents error.
> Steps to reproduce:
> 1. Disable Job, Do Not Initial Initiate Perforce Sync and let
> 2. Navigate -> Jenkins -> Job (job must be using Perforce as SCM) -> Workspace
> Note: in step two, workspace contains text declaring the following:
> Error: no workspace
> A project won't have any workspace until at least one build is performed.
> Run a build to have Jenkins create a workspace.
> 3. Click link "Run a build to have Jenkins create a workspace."
> Error Returned:
> java.io.IOException: $JOBNAME is not buildable.
--
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
