[JIRA] (JENKINS-12889) Jenkins "Workspace" presents "Run a build" even when Builds are Disabled

Colin Johnson created JENKINS-12889:
---------------------------------------

             Summary: 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: perforce
    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

       

     [ 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

       

    [ https://issues.jenkins-ci.org/browse/JENKINS-12889?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160250#comment-160250 ]

SCM/JIRA link daemon commented on JENKINS-12889:
------------------------------------------------

Code changed in jenkins
User: Andrew Bayer
Path:
 core/src/main/resources/hudson/model/AbstractItem/noWorkspace.jelly
http://jenkins-ci.org/commit/jenkins/9ffcbba5e96ea508419171c0ff1d18a5fdc88c4a
Log:
  Merge pull request #404 from onemanbucket/master

fixes: JENKINS-12889 Jenkins "Workspace" presents "Run a build" even when Builds are Disabled





               

> 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

       

SCM/JIRA link daemon commented on JENKINS-12889

Jenkins "Workspace" presents "Run a build" even when Builds are Disabled

Code changed in jenkins User: Erik Lindblad Path: core/src/main/resources/hudson/model/AbstractItem/noWorkspace.jelly http://jenkins-ci.org/commit/jenkins/4f44e613e826f476d861d83df6370d2ea976bcdd Log: Fixes JENKINS-12889

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Colin Johnson resolved JENKINS-12889 as Fixed

Jenkins "Workspace" presents "Run a build" even when Builds are Disabled

1. Disable Job, Do Not Initial Initiate Perforce Sync and let 2. Navigate -> Jenkins -> Job (job must be using Perforce as SCM) -> Workspace When in Workspace "Build" is now disabled with the following message: "Error: no workspace There's no workspace for this project. Possible reasons are: The project was renamed recently and no build was done under the new name. The slave this project has run on for the last time was removed. The workspace directory (null) is removed outside Jenkins. The workspace was wiped out and no build has been done since then."
Change By:	Colin Johnson (01/Sep/12 6:13 AM)
Status:	Open Resolved
Resolution:	Fixed

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Colin Johnson resolved JENKINS-12889 as Fixed

Jenkins "Workspace" presents "Run a build" even when Builds are Disabled

Change By:	Colin Johnson (01/Sep/12 6:14 AM)
Status:	Reopened Resolved
Resolution:	Fixed

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Colin Johnson closed JENKINS-12889 as Fixed

Jenkins "Workspace" presents "Run a build" even when Builds are Disabled

Change By:	Colin Johnson (01/Sep/12 6:14 AM)
Status:	Resolved Closed

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Colin Johnson closed JENKINS-12889 as Fixed

Jenkins "Workspace" presents "Run a build" even when Builds are Disabled

Change By:	Colin Johnson (01/Sep/12 6:13 AM)
Status:	Resolved Closed

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Colin Johnson reopened JENKINS-12889

Jenkins "Workspace" presents "Run a build" even when Builds are Disabled

Change By:	Colin Johnson (01/Sep/12 6:14 AM)
Resolution:	Fixed
Status:	Closed Reopened

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

 

Colin Johnson edited a comment on JENKINS-12889

Jenkins "Workspace" presents "Run a build" even when Builds are Disabled

Have verified that issue is no longer present - followed the following steps: 1. Disable Job, Do Not Initial Initiate Perforce Sync and let 2. Navigate -> Jenkins -> Job (job must be using Perforce as SCM) -> Workspace When in Workspace "Build" is now disabled with the following message: "Error: no workspace There's no workspace for this project. Possible reasons are: The project was renamed recently and no build was done under the new name. The slave this project has run on for the last time was removed. The workspace directory (null) is removed outside Jenkins. The workspace was wiped out and no build has been done since then."

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira