![]() |
|
|
|
|
Issue Type:
|
![Bug]() Bug
|
|
Assignee:
|
Rob Petti
|
|
Components:
|
perforce |
|
Created:
|
05/Dec/13 6:02 AM
|
|
Description:
|
I have setup a job to poll perforce using the perforce plugin. I have the viewspec defined and selected "let jenkins create workspace". Now, there are a couple of things I observer and would like to understand why this is the way its happening.
1). I'm not able to access the workspace that Jenkins created using p4v. when I search the workspace shows-up briefly and disappears when/before I can select it. very strange. I can't access them through p4 cmd line interface as well with "p4 workspaces". They do show up in p4v momentarily when I search but cant touch them or they disappear. Why is this so? and this is not allowing me to delete old workspaces from p4.
2). When I update the viewspec to a different depot location and save the job. The next run switches back to the old viewspec and when I go to configure I see that the viewspec changes I made were reverted. The build log shows "Using master perforce client: temp_workspace" and uses the old viewspec to poll and sync. So, my main question is Why can't I update the viewspec?
are the viewspec stored in Jenkins (or) p4? Is the viewspec updated in p4 when i saved the job config (or) when I build?
The combination of both these issues is making me create a new job everytime I want to update the viewspec without a way to delete the old workspaces in p4.
Thanks for any help, this has been driving me crazy.
Sri
|
|
Environment:
|
Jenkins 1.509.2
Perforce 1.3.24
|
|
Project:
|
Jenkins
|
|
Priority:
|
![Critical]() Critical
|
|
Reporter:
|
Sri V
|
|
|
|
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
|
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
[email protected].
For more options, visit
https://groups.google.com/groups/opt_out.
