![]() |
|
|
|
|
Issue Type:
|
![Bug]() Bug
|
|
Affects Versions:
|
current |
|
Assignee:
|
Rob Petti
|
|
Components:
|
perforce |
|
Created:
|
14/Jun/13 8:58 AM
|
|
Description:
|
Hello,
We have experienced several issues with substitution of parameters during execution of operation.
For example, ${EXECUTOR_NUMBER} works well for checkout(), but this parameter is not accessible during execution processWorkspaceBeforeDeletion(). It causes corruption of job, which requires manual fix at server’s side. Reproduction steps:
• We start job, and checkout() successfully creates workspace.
• Cleanup workspace…
• getWorkspace() in processWorkspaceBeforeDeletion() creates new workspace at Perforce server (name contains unsubstituted EXECUTOR_NUMBER parameter) and then deletes it. BTW, it deletes local folders as well.
• Run job again…
• Checkout() completes successfully, because P4 server thinks that workspace is up to date
• Job fails, because there’s no data in job’s workspace after p4 checkout
Best regards,
Oleg Nenashev
|
|
Project:
|
Jenkins
|
|
Labels:
|
job
workspace_corruption
|
|
Priority:
|
![Critical]() Critical
|
|
Reporter:
|
Oleg Nenashev
|
|
|
|
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.
