Change By: Chung Yee Liew (14/Feb/13 1:11 AM)
Description: While Not using Coverity Plugin :
Building in workspace C:\Program Files (x86)\Jenkins\jobs\Demo\workspace
Using master perforce client: coverity_demo_win
[workspace] $ "C:\Program Files\Perforce\p4.exe" -P 2724A1B5872D6C885C36A8633DEEEE3A workspace -o coverity_demo_win
'Don't update client' is set. Not saving the client changes.
Note: .repository directory in workspace (if exists) is skipped during clean.
Quickly cleaning workspace...
.
.
.
.
Build succeeded.
.
.
.
.
Time Elapsed 00:01:28.86

While Using Coverity Plugin:
Building in workspace C:\Program Files (x86)\Jenkins\jobs\Demo\workspace
Using master perforce client: coverity_demo_Win
[workspace] $ "C:\Program Files\Coverity\Coverity Static Analysis\bin\cov-build" --dir C:\Demo\coverity --instrument --encoding UTF-8 --enable-pch C:\Windows\Microsoft.NET\Framework\v4.0.30319\MSBuild.exe C:\demo\win32\vc10\demotest.sln /p:configuration=Release /p:platform=x64 /nr:false "C:\Program Files\Perforce\p4.exe" workspace -o coverity_demo_win
*** Perforce client workspace 'coverity_demo_win' doesn't exist.
*** Please create it, or allow Jenkins to manage clients on it's own.
*** If the client name mentioned above is not what you expected, 
*** check your 'Client name format for slaves' advanced config option.
ERROR: Error accessing perforce workspace.
Finished: FAILURE

Please note workspace "coverity_demo_win" does exist.
The error occur while coverity plugin is enable.
When Coverity plugin is disable Perforce plugin were about to sync & build without any issue.

Coverity plugin interfere with perforce commands.
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.
 
 

Reply via email to