[JIRA] [p4-plugin] (JENKINS-24070) Error: Wipe Out Workspace blocked by SCM

197 views
Skip to first unread message

pallen@perforce.com (JIRA)

unread,
Sep 11, 2015, 10:35:01 AM9/11/15
to jenkinsc...@googlegroups.com
Paul Allen closed an issue as Fixed
 

Old Issue.

Jenkins / Bug JENKINS-24070
Error: Wipe Out Workspace blocked by SCM
Change By: Paul Allen
Status: Reopened Closed
Resolution: Fixed
Add Comment Add Comment
 
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
Atlassian logo

squalou.jenkins@gmail.com (JIRA)

unread,
Apr 20, 2016, 8:16:02 AM4/20/16
to jenkinsc...@googlegroups.com
squalou jenkins reopened an issue
 

Hi,

I'm using p4 plugin 1.3.9 on jenkins LTS 1.642.3, with linux masters, and a mix of linux and solaris slaves.

The problem still exists, as initially reported. Choosing "Wipe out workspace" ends with a message stating that the operation is "blocked by SCM"

That's really annoying.

Change By: squalou jenkins
Resolution: Fixed
Status: Closed Reopened

pallen@perforce.com (JIRA)

unread,
Apr 21, 2016, 3:03:02 PM4/21/16
to jenkinsc...@googlegroups.com
Paul Allen commented on Bug JENKINS-24070
 
Re: Error: Wipe Out Workspace blocked by SCM

Are their files open within the workspace?

If you have used shelving or opened a file for edit then it may prevent the workspace from being deleted. Still it is a SIR for me to revert any pending files. If there are no files opened then it still remains a mystery as to what is preventing the deleting of the Workspace.

scm_issue_link@java.net (JIRA)

unread,
Apr 22, 2016, 1:12:02 AM4/22/16
to jenkinsc...@googlegroups.com

Code changed in jenkins
User: Paul Allen
Path:
src/main/java/org/jenkinsci/plugins/p4/client/ClientHelper.java
src/main/java/org/jenkinsci/plugins/p4/tasks/RemoveClientTask.java
http://jenkins-ci.org/commit/p4-plugin/d6dbb7bf0805e4ee7bd76d6ae819daaeb5e0a0f1
Log:
Revert files before deleting a Workspace.

JENKINS-24070

Jenkins Log (successful delete):
Apr 21, 2016 10:08:20 PM org.jenkinsci.plugins.p4.PerforceScm
processWorkspaceBeforeDeletion
INFO: processWorkspaceBeforeDeletion
Apr 21, 2016 10:08:20 PM
org.jenkinsci.plugins.p4.tasks.RemoveClientTask invoke
INFO: Task: remove client.
Apr 21, 2016 10:08:20 PM
org.jenkinsci.plugins.p4.tasks.RemoveClientTask invoke
INFO: P4: unsyncing client: jenkins-master-open
Apr 21, 2016 10:08:20 PM
org.jenkinsci.plugins.p4.tasks.RemoveClientTask invoke
INFO: P4: remove client: jenkins-master-open
Apr 21, 2016 10:08:20 PM org.jenkinsci.plugins.p4.PerforceScm
processWorkspaceBeforeDeletion
INFO: clean: true

squalou.jenkins@gmail.com (JIRA)

unread,
Apr 22, 2016, 4:10:02 AM4/22/16
to jenkinsc...@googlegroups.com

There probably were no open files, I'll test again to check.

Additional info that may be helpful :

  • sync was done with MODTIME, without ALLWRITE, and in SYNC ONLY mode, without populating the have list.

pallen@perforce.com (JIRA)

unread,
Apr 22, 2016, 1:20:01 PM4/22/16
to jenkinsc...@googlegroups.com

Can you let me know if the owner of the workspace differs from the user in the Jenkins 'Perforce Credential' as it could be a permission issue. Perhaps the client workspace has been set to locked?

squalou.jenkins@gmail.com (JIRA)

unread,
Apr 23, 2016, 5:04:01 AM4/23/16
to jenkinsc...@googlegroups.com

To make things clear (because I'm often lost in translation) :

  • there's the 'Jenkins 's job worksapce'
  • there's a 'p4 workspace ' or 'p4 client'

So, Indeed :

'jenkins's workspace' owner is 'jenkins', and p4 user use to sync is completely different.
On top of that, we often use 'custom workspaces' option in job configuration (not sure it matters).

All this being said I have no idea what you mean by 'locked workspace'.

thx,

pallen@perforce.com (JIRA)

unread,
Apr 25, 2016, 3:57:01 AM4/25/16
to jenkinsc...@googlegroups.com

I'm interested in the owner of the p4 client workspace and the p4 user trying to delete it. In a normal situation these would be the same, but of they were different then the user may not have permissions to delete it (unless 'admin' or 'super').

The lock option is in the client view, to prevent other users changing the workspace.

Client: admin
Update: 2016/01/22 13:53:38
Access: 2016/04/06 18:42:23
Owner: pallen
Description:
Created by pallen.

Root: /Users/pallen/Perforce/1666/ws
Options: noallwrite noclobber nocompress unlocked nomodtime normdir
SubmitOptions: submitunchanged
LineEnd: local
View:
//depot/... //admin/depot/...

squalou.jenkins@gmail.com (JIRA)

unread,
May 3, 2016, 3:51:01 AM5/3/16
to jenkinsc...@googlegroups.com

Hi,
sorry for the delay,
I think the problem is now working.

I checked : t was not a 'lock' issue.

On the other hand, I added some parameters in the global configuration of the plugin. (jenkins/configure)
Perforce: OnDelete Workspace Options
I ticked delete perforce client and delete workspace files.

Seems to work now.

To conclude I'd say :

  • why do these options exist at all,
  • why are they 'global', if they make sense they should be customizable per project
  • and it's very hard to guess there's an option here only whith the 'scm is blocking' error message when trying to wipeout
    the workspace.

anyway, thanks a lot for your answers !

pallen@perforce.com (JIRA)

unread,
May 3, 2016, 5:29:02 AM5/3/16
to jenkinsc...@googlegroups.com

Thanks for letting me know.

The Global options can be confusing, but the original use-case was for a customer trying to clean up 100's of Client Workspaces, but keeping the content. Global seemed easier to manage, as it avoided having to go into each Jenkins Job Configuration before deleting it.

Perhaps something for the docs...

pallen@perforce.com (JIRA)

unread,
May 6, 2016, 8:46:02 AM5/6/16
to jenkinsc...@googlegroups.com
Paul Allen started work on Bug JENKINS-24070
 
Change By: Paul Allen
Status: Reopened In Progress

pallen@perforce.com (JIRA)

unread,
May 6, 2016, 8:53:02 AM5/6/16
to jenkinsc...@googlegroups.com
Paul Allen resolved as Fixed
 
Change By: Paul Allen
Status: In Progress Resolved
Resolution: Fixed

pallen@perforce.com (JIRA)

unread,
May 18, 2016, 6:54:11 AM5/18/16
to jenkinsc...@googlegroups.com
Paul Allen closed an issue as Fixed
 

Released in 1.3.9

Change By: Paul Allen
Status: Resolved Closed

dantran@gmail.com (JIRA)

unread,
May 21, 2016, 5:18:02 PM5/21/16
to jenkinsc...@googlegroups.com
dan tran reopened an issue
 

still see this issue at 1.3.9. I am not going to revert back to 1.3.5 and see if I can help Paul to trouble shoot this issue

Change By: dan tran
Resolution: Fixed
Status: Closed Reopened

dantran@gmail.com (JIRA)

unread,
May 21, 2016, 5:23:02 PM5/21/16
to jenkinsc...@googlegroups.com
dan tran resolved as Fixed
Change By: dan tran
Status: Reopened Resolved
Resolution: Fixed

dantran@gmail.com (JIRA)

unread,
May 21, 2016, 5:23:02 PM5/21/16
to jenkinsc...@googlegroups.com
dan tran commented on Bug JENKINS-24070
 
Re: Error: Wipe Out Workspace blocked by SCM

ah, it works now, i just need to setup the global configuration for perforce plugin to remove client as well. s

pallen@perforce.com (JIRA)

unread,
Jul 8, 2016, 4:56:07 AM7/8/16
to jenkinsc...@googlegroups.com
Paul Allen closed an issue as Fixed
 

Released.

Change By: Paul Allen
Status: Resolved Closed
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
Atlassian logo
Reply all
Reply to author
Forward
0 new messages