Jenkins CI › Jenkins issues

[JIRA] (JENKINS-13890) FATAL: Unable to retrieve WorkItem data at this point.

Classic

List

Threaded

6 messages Options

JIRA noreply@jenkins-ci.org

[JIRA] (JENKINS-13890) FATAL: Unable to retrieve WorkItem data at this point.

Ferenc Kovacs created JENKINS-13890:
---------------------------------------

Summary: FATAL: Unable to retrieve WorkItem data at this point.
Key: JENKINS-13890
URL: https://issues.jenkins-ci.org/browse/JENKINS-13890
Project: Jenkins
Issue Type: Bug
Components: integrity-plugin
Affects Versions: current
Environment: Win7 64bit with Jenkins ver. 1.465,
PTC plugin 1.13
Reporter: Ferenc Kovacs
Assignee: Cletus D'Souza
Fix For: current

Cletus, I am having problems using this plugin for a large mks project (25K files). I have turned debugging on with: -Dorg.apache.commons.logging.simplelog.log.IntegritySCM=debug.

I also gave the Jenkins JVM 1.5GB of heap space, just to be on the safe side.

>>> The exception I get is:

Started by user anonymous
Building in workspace C:\Jenkins\jobs\MKS Test\workspace
Change Log: http://pc11065:8080/job/MKS%20Test/13/changes
Build Log: http://pc11065:8080/job/MKS%20Test/13/console
Preparing to execute si projectinfo for #p=p:/PROJEKTE/MPA/mpa.pj#s=PC_SW/pc_sw.pj#
Preparing to execute si viewproject for #p=p:/PROJEKTE/MPA/MPA.pj#s=PC_SW/pc_sw.pj
An API Exception was caught!
FATAL: Unable to retrieve WorkItem data at this point.

>>> jenkins.err.log:

INFO: Jenkins is fully up and running
May 24, 2012 10:23:40 AM [DEBUG] IntegritySCM - IntegritySCM.getDescriptor() invoked...!
May 24, 2012 10:23:40 AM [DEBUG] IntegritySCM - IntegritySCM.getDescriptor() invoked...!
May 24, 2012 10:23:40 AM [DEBUG] IntegritySCM - IntegritySCM.getDescriptor() invoked...!
May 24, 2012 10:23:40 AM [DEBUG] IntegritySCM - IntegritySCM.getDescriptor() invoked...!
May 24, 2012 10:23:40 AM [DEBUG] IntegritySCM - IntegritySCM.getDescriptor() invoked...!
May 24, 2012 10:23:40 AM [DEBUG] IntegritySCM - IntegritySCM.getDescriptor() invoked...!
May 24, 2012 10:23:40 AM [DEBUG] IntegritySCM - IntegritySCM.getDescriptor() invoked...!
May 24, 2012 10:23:40 AM [DEBUG] IntegritySCM - IntegritySCM.getDescriptor() invoked...!
May 24, 2012 10:23:40 AM [DEBUG] IntegritySCM - IntegrityItemAction.IntegrityItemDescriptorImpl.isApplicable executed!
May 24, 2012 10:23:50 AM [DEBUG] IntegritySCM - Start execution of checkout() routine...!
May 24, 2012 10:23:50 AM [DEBUG] IntegritySCM - Creating Integrity API Session...
May 24, 2012 10:23:50 AM [DEBUG] IntegritySCM - IntegritySCM.getDescriptor() invoked...!
May 24, 2012 10:23:50 AM [DEBUG] IntegritySCM - IntegritySCM.getDescriptor() invoked...!
May 24, 2012 10:23:50 AM [DEBUG] IntegritySCM - IntegritySCM.getDescriptor() invoked...!
May 24, 2012 10:23:50 AM [DEBUG] IntegritySCM - IntegritySCM.getDescriptor() invoked...!
May 24, 2012 10:23:50 AM [DEBUG] IntegritySCM - IntegritySCM.getDescriptor() invoked...!
May 24, 2012 10:23:50 AM [DEBUG] IntegritySCM - IntegritySCM.getDescriptor() invoked...!
May 24, 2012 10:23:50 AM [DEBUG] IntegritySCM - IntegritySCM.getDescriptor() invoked...!
May 24, 2012 10:23:50 AM [DEBUG] IntegritySCM - IntegritySCM.getDescriptor() invoked...!
May 24, 2012 10:23:50 AM [DEBUG] IntegritySCM - IntegrityItemAction.IntegrityItemDescriptorImpl.isApplicable executed!
May 24, 2012 10:23:51 AM [DEBUG] IntegritySCM - api ping --user=build_2050 --port=7001 --hostname=MKS-4 -- returned exit code 0
May 24, 2012 10:23:51 AM [DEBUG] IntegritySCM - Successfully established connection build_2050@MKS-4:7001
May 24, 2012 10:23:51 AM [DEBUG] IntegritySCM - Preparing to execute si projectinfo for #p=p:/PROJEKTE/MPA/MPA.pj#s=PC_SW/pc_sw.pj#
May 24, 2012 10:23:51 AM [DEBUG] IntegritySCM - si projectinfo --user=build_2050 --port=7001 --hostname=MKS-4 --project=#p=p:/PROJEKTE/MPA/MPA.pj#s=PC_SW/pc_sw.pj# -- returned exit code 0
May 24, 2012 10:23:51 AM [DEBUG] IntegritySCM - si projectinfo --user=build_2050 --port=7001 --hostname=MKS-4 --project=#p=p:/PROJEKTE/MPA/MPA.pj#s=PC_SW/pc_sw.pj# -- returned 0
May 24, 2012 10:23:51 AM [DEBUG] IntegritySCM - Preparing to execute si viewproject for #p=p:/PROJEKTE/MPA/MPA.pj#s=PC_SW/pc_sw.pj
May 24, 2012 10:23:52 AM [DEBUG] IntegritySCM - Executed si viewproject --user=build_2050 --port=7001 --hostname=MKS-4 --recurse --project=#p=p:/PROJEKTE/MPA/MPA.pj#s=PC_SW/pc_sw.pj --fields=name,context,cpid,memberrev,membertimestamp,memberdescription -- with interim
May 24, 2012 10:23:52 AM [DEBUG] IntegritySCM - Attempting to open connection to database: C:\Jenkins\jobs\MKS Test\builds\2012-05-24_10-23-50\IntegritySCM
May 24, 2012 10:23:53 AM [DEBUG] IntegritySCM - Schema 'DBUSER' does not exist
May 24, 2012 10:23:53 AM [DEBUG] IntegritySCM - Integrity SCM cache tables do not exist, creating...
May 24, 2012 10:23:53 AM [DEBUG] IntegritySCM - New Integrity SCM cache tables successfully created!
May 24, 2012 10:23:53 AM [DEBUG] IntegritySCM - Attempting to execute query INSERT INTO CM_PROJECT (TYPE, NAME, MEMBER_ID, TIMESTAMP, DESCRIPTION, CONFIG_PATH, REVISION, RELATIVEFILE) VALUES (?, ?, ?, ?, ?, ?, ?, ?)
May 24, 2012 10:24:13 AM [INFO] IntegritySCM - API Exception caught...
May 24, 2012 10:24:14 AM [DEBUG] IntegritySCM - Attempting to shut down database: C:\Jenkins\jobs\MKS Test\builds\2012-05-24_10-23-50\IntegritySCM
May 24, 2012 10:24:14 AM [INFO] IntegritySCM - Failed to shutdown database connection!
May 24, 2012 10:24:14 AM [INFO] IntegritySCM - Database 'C:/Jenkins/jobs/MKS Test/builds/2012-05-24_10-23-50/IntegritySCM' shutdown.
May 24, 2012 10:24:14 AM [INFO] IntegritySCM - java.sql.SQLNonTransientConnectionException: Database 'C:/Jenkins/jobs/MKS Test/builds/2012-05-24_10-23-50/IntegritySCM' shutdown.
May 24, 2012 10:24:14 AM [DEBUG] IntegritySCM - Successfully disconnected connection build_2050@MKS-4:7001

>>> However, if I try this with a sub-subproject (3K files) it seems to work:

Started by user anonymous
Building in workspace C:\Jenkins\jobs\MKS Test\workspace
Change Log: http://pc11065:8080/job/MKS%20Test/16/changes
Build Log: http://pc11065:8080/job/MKS%20Test/16/console
Preparing to execute si projectinfo for #p=p:/PROJEKTE/MPA/PC_SW/pc_sw.pj#s=SRC/src.pj
Preparing to execute si viewproject for #p=p:/PROJEKTE/MPA/PC_SW/pc_sw.pj#s=SRC/src.pj
Checkout directory is C:\Jenkins\jobs\MKS Test\workspace
A clean copy is requested; deleting contents of C:\Jenkins\jobs\MKS Test\workspace
Populating clean workspace...
Successfully checked out 2175 files!
Saving current Integrity Project configuration...
Writing build change log...
Change log successfully generated: C:\Jenkins\jobs\MKS Test\builds\2012-05-23_19-28-14\changelog.xml
Finished: SUCCESS

>>> I have also updated mksapi.jar to the one I have in my client, plus executed the mksapiviewer: c:\Jenkins\jobs>mksapiviewer --xml --iplocal si viewproject -R --project=#p=p:/PROJEKTE/MPA/PC_SW/pc_sw.pj# --fields=name,context > mksview.log

I get a 9MB file with a fine looking xml structure, with a bunch of WorkItems:

<?xml version="1.0"?>
<Response command="viewproject" app="si" version="4.10.0 7-1 9665">
<App-Connection port="7001" userID="build_2050" server="MKS-4"></App-Connection>
<WorkItems selectionType="ICurrentOrFormerProjectTypeElementSelection">
<WorkItem id="#p=p:/PROJEKTE/MPA/PC_SW/pc_sw.pj#boost" parentID="#p=p:/PROJEKTE/MPA/PC_SW/pc_sw.pj" displayId="p:/PROJEKTE/MPA/PC_SW/boost/project.pj" modelType="si.Subproject">
<Field name="name">
<Value dataType="string">p:/PROJEKTE/MPA/PC_SW/boost/project.pj</Value>
</Field>
<Field name="parent">
<Value dataType="string">p:/PROJEKTE/MPA/PC_SW/pc_sw.pj</Value>
</Field>
<Field name="type">
<Value dataType="string">shared-build-subproject</Value>
</Field>
<Field name="memberrev">
<Item id="1.1.1.31" displayId="1.1.1.31" modelType="si.Revision">
</Item>
</Field>
</WorkItem>
<WorkItem .........................................

Please help out :) Thanks!

--
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

JIRA noreply@jenkins-ci.org

[JIRA] (JENKINS-13890) FATAL: Unable to retrieve WorkItem data at this point.

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

Cletus D'Souza commented on JENKINS-13890:
------------------------------------------

Few questions:
1) You mentioned you've updated the mksapi.jar in the plugin... so, what version of the client are you running?
2) What is the Integrity Server version?
3) Was this a problem with 1.12 version of the Jenkins plugin?

> FATAL: Unable to retrieve WorkItem data at this point.
> ------------------------------------------------------
>
> Key: JENKINS-13890
> URL: https://issues.jenkins-ci.org/browse/JENKINS-13890
> Project: Jenkins
> Issue Type: Bug
> Components: integrity-plugin
> Affects Versions: current
> Environment: Win7 64bit with Jenkins ver. 1.465,
> PTC plugin 1.13
> Reporter: Ferenc Kovacs
> Assignee: Cletus D'Souza
> Labels: exception, plugin, windows
> Fix For: current
>
>
> Cletus, I am having problems using this plugin for a large mks project (25K files). I have turned debugging on with: -Dorg.apache.commons.logging.simplelog.log.IntegritySCM=debug.
> I also gave the Jenkins JVM 1.5GB of heap space, just to be on the safe side.
> >>> The exception I get is:
> Started by user anonymous
> Building in workspace C:\Jenkins\jobs\MKS Test\workspace
> Change Log: http://pc11065:8080/job/MKS%20Test/13/changes
> Build Log: http://pc11065:8080/job/MKS%20Test/13/console
> Preparing to execute si projectinfo for #p=p:/PROJEKTE/MPA/mpa.pj#s=PC_SW/pc_sw.pj#
> Preparing to execute si viewproject for #p=p:/PROJEKTE/MPA/MPA.pj#s=PC_SW/pc_sw.pj
> An API Exception was caught!
> FATAL: Unable to retrieve WorkItem data at this point.
> >>> jenkins.err.log:
> INFO: Jenkins is fully up and running
> May 24, 2012 10:23:40 AM [DEBUG] IntegritySCM - IntegritySCM.getDescriptor() invoked...!
> May 24, 2012 10:23:40 AM [DEBUG] IntegritySCM - IntegritySCM.getDescriptor() invoked...!
> May 24, 2012 10:23:40 AM [DEBUG] IntegritySCM - IntegritySCM.getDescriptor() invoked...!
> May 24, 2012 10:23:40 AM [DEBUG] IntegritySCM - IntegritySCM.getDescriptor() invoked...!
> May 24, 2012 10:23:40 AM [DEBUG] IntegritySCM - IntegritySCM.getDescriptor() invoked...!
> May 24, 2012 10:23:40 AM [DEBUG] IntegritySCM - IntegritySCM.getDescriptor() invoked...!
> May 24, 2012 10:23:40 AM [DEBUG] IntegritySCM - IntegritySCM.getDescriptor() invoked...!
> May 24, 2012 10:23:40 AM [DEBUG] IntegritySCM - IntegritySCM.getDescriptor() invoked...!
> May 24, 2012 10:23:40 AM [DEBUG] IntegritySCM - IntegrityItemAction.IntegrityItemDescriptorImpl.isApplicable executed!
> May 24, 2012 10:23:50 AM [DEBUG] IntegritySCM - Start execution of checkout() routine...!
> May 24, 2012 10:23:50 AM [DEBUG] IntegritySCM - Creating Integrity API Session...
> May 24, 2012 10:23:50 AM [DEBUG] IntegritySCM - IntegritySCM.getDescriptor() invoked...!
> May 24, 2012 10:23:50 AM [DEBUG] IntegritySCM - IntegritySCM.getDescriptor() invoked...!
> May 24, 2012 10:23:50 AM [DEBUG] IntegritySCM - IntegritySCM.getDescriptor() invoked...!
> May 24, 2012 10:23:50 AM [DEBUG] IntegritySCM - IntegritySCM.getDescriptor() invoked...!
> May 24, 2012 10:23:50 AM [DEBUG] IntegritySCM - IntegritySCM.getDescriptor() invoked...!
> May 24, 2012 10:23:50 AM [DEBUG] IntegritySCM - IntegritySCM.getDescriptor() invoked...!
> May 24, 2012 10:23:50 AM [DEBUG] IntegritySCM - IntegritySCM.getDescriptor() invoked...!
> May 24, 2012 10:23:50 AM [DEBUG] IntegritySCM - IntegritySCM.getDescriptor() invoked...!
> May 24, 2012 10:23:50 AM [DEBUG] IntegritySCM - IntegrityItemAction.IntegrityItemDescriptorImpl.isApplicable executed!
> May 24, 2012 10:23:51 AM [DEBUG] IntegritySCM - api ping --user=build_2050 --port=7001 --hostname=MKS-4 -- returned exit code 0
> May 24, 2012 10:23:51 AM [DEBUG] IntegritySCM - Successfully established connection build_2050@MKS-4:7001
> May 24, 2012 10:23:51 AM [DEBUG] IntegritySCM - Preparing to execute si projectinfo for #p=p:/PROJEKTE/MPA/MPA.pj#s=PC_SW/pc_sw.pj#
> May 24, 2012 10:23:51 AM [DEBUG] IntegritySCM - si projectinfo --user=build_2050 --port=7001 --hostname=MKS-4 --project=#p=p:/PROJEKTE/MPA/MPA.pj#s=PC_SW/pc_sw.pj# -- returned exit code 0
> May 24, 2012 10:23:51 AM [DEBUG] IntegritySCM - si projectinfo --user=build_2050 --port=7001 --hostname=MKS-4 --project=#p=p:/PROJEKTE/MPA/MPA.pj#s=PC_SW/pc_sw.pj# -- returned 0
> May 24, 2012 10:23:51 AM [DEBUG] IntegritySCM - Preparing to execute si viewproject for #p=p:/PROJEKTE/MPA/MPA.pj#s=PC_SW/pc_sw.pj
> May 24, 2012 10:23:52 AM [DEBUG] IntegritySCM - Executed si viewproject --user=build_2050 --port=7001 --hostname=MKS-4 --recurse --project=#p=p:/PROJEKTE/MPA/MPA.pj#s=PC_SW/pc_sw.pj --fields=name,context,cpid,memberrev,membertimestamp,memberdescription -- with interim
> May 24, 2012 10:23:52 AM [DEBUG] IntegritySCM - Attempting to open connection to database: C:\Jenkins\jobs\MKS Test\builds\2012-05-24_10-23-50\IntegritySCM
> May 24, 2012 10:23:53 AM [DEBUG] IntegritySCM - Schema 'DBUSER' does not exist
> May 24, 2012 10:23:53 AM [DEBUG] IntegritySCM - Integrity SCM cache tables do not exist, creating...
> May 24, 2012 10:23:53 AM [DEBUG] IntegritySCM - New Integrity SCM cache tables successfully created!
> May 24, 2012 10:23:53 AM [DEBUG] IntegritySCM - Attempting to execute query INSERT INTO CM_PROJECT (TYPE, NAME, MEMBER_ID, TIMESTAMP, DESCRIPTION, CONFIG_PATH, REVISION, RELATIVEFILE) VALUES (?, ?, ?, ?, ?, ?, ?, ?)
> May 24, 2012 10:24:13 AM [INFO] IntegritySCM - API Exception caught...
> May 24, 2012 10:24:14 AM [DEBUG] IntegritySCM - Attempting to shut down database: C:\Jenkins\jobs\MKS Test\builds\2012-05-24_10-23-50\IntegritySCM
> May 24, 2012 10:24:14 AM [INFO] IntegritySCM - Failed to shutdown database connection!
> May 24, 2012 10:24:14 AM [INFO] IntegritySCM - Database 'C:/Jenkins/jobs/MKS Test/builds/2012-05-24_10-23-50/IntegritySCM' shutdown.
> May 24, 2012 10:24:14 AM [INFO] IntegritySCM - java.sql.SQLNonTransientConnectionException: Database 'C:/Jenkins/jobs/MKS Test/builds/2012-05-24_10-23-50/IntegritySCM' shutdown.
> May 24, 2012 10:24:14 AM [DEBUG] IntegritySCM - Successfully disconnected connection build_2050@MKS-4:7001
> >>> However, if I try this with a sub-subproject (3K files) it seems to work:
> Started by user anonymous
> Building in workspace C:\Jenkins\jobs\MKS Test\workspace
> Change Log: http://pc11065:8080/job/MKS%20Test/16/changes
> Build Log: http://pc11065:8080/job/MKS%20Test/16/console
> Preparing to execute si projectinfo for #p=p:/PROJEKTE/MPA/PC_SW/pc_sw.pj#s=SRC/src.pj
> Preparing to execute si viewproject for #p=p:/PROJEKTE/MPA/PC_SW/pc_sw.pj#s=SRC/src.pj
> Checkout directory is C:\Jenkins\jobs\MKS Test\workspace
> A clean copy is requested; deleting contents of C:\Jenkins\jobs\MKS Test\workspace
> Populating clean workspace...
> Successfully checked out 2175 files!
> Saving current Integrity Project configuration...
> Writing build change log...
> Change log successfully generated: C:\Jenkins\jobs\MKS Test\builds\2012-05-23_19-28-14\changelog.xml
> Finished: SUCCESS
> >>> I have also updated mksapi.jar to the one I have in my client, plus executed the mksapiviewer: c:\Jenkins\jobs>mksapiviewer --xml --iplocal si viewproject -R --project=#p=p:/PROJEKTE/MPA/PC_SW/pc_sw.pj# --fields=name,context > mksview.log
> I get a 9MB file with a fine looking xml structure, with a bunch of WorkItems:
> <?xml version="1.0"?>
> <Response command="viewproject" app="si" version="4.10.0 7-1 9665">
> <App-Connection port="7001" userID="build_2050" server="MKS-4"></App-Connection>
> <WorkItems selectionType="ICurrentOrFormerProjectTypeElementSelection">
> <WorkItem id="#p=p:/PROJEKTE/MPA/PC_SW/pc_sw.pj#boost" parentID="#p=p:/PROJEKTE/MPA/PC_SW/pc_sw.pj" displayId="p:/PROJEKTE/MPA/PC_SW/boost/project.pj" modelType="si.Subproject">
> <Field name="name">
> <Value dataType="string">p:/PROJEKTE/MPA/PC_SW/boost/project.pj</Value>
> </Field>
> <Field name="parent">
> <Value dataType="string">p:/PROJEKTE/MPA/PC_SW/pc_sw.pj</Value>
> </Field>
> <Field name="type">
> <Value dataType="string">shared-build-subproject</Value>
> </Field>
> <Field name="memberrev">
> <Item id="1.1.1.31" displayId="1.1.1.31" modelType="si.Revision">
> </Item>
> </Field>
> </WorkItem>
> <WorkItem .........................................
> Please help out :) Thanks!

--
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

JIRA noreply@jenkins-ci.org

[JIRA] (JENKINS-13890) FATAL: Unable to retrieve WorkItem data at this point.

In reply to this post by JIRA noreply@jenkins-ci.org

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

Ferenc Kovacs commented on JENKINS-13890:
-----------------------------------------

Cletus, I have finally found the root cause... A sub-sub-sub project was messed up somehow by a developer. When trying to open it in Integrity Client, it fatal error-ed back with: "Cannot show view information: Members were added that had already existed". So that's about it.

It is interesting however, that we can checkout and work with all projects with the client GUI except the unimportant broken one, but with the Jenkins plugin, no files can be retrieved. It is also impossible to drop the broken project, since no operation can be performed on it.
... third week of waiting for MKS support to reply.

JIRA noreply@jenkins-ci.org

[JIRA] (JENKINS-13890) FATAL: Unable to retrieve WorkItem data at this point.

In reply to this post by JIRA noreply@jenkins-ci.org

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

Ferenc Kovacs edited comment on JENKINS-13890 at 6/11/12 4:57 PM:
------------------------------------------------------------------

Cletus, I have finally found the root cause... A sub-sub-sub project was messed up somehow by a developer. When trying to open it in Integrity Client, it fatal error-ed back with: "Cannot show view information: Members were added that had already existed". So that's about it.

It is interesting however, that we can checkout and work with all projects with the client GUI except the unimportant broken one, but with the Jenkins plugin, no files can be retrieved. The broken sub-project seems to contaminate the whole project tree. It is also impossible to drop the broken project, since no operation can be performed on it.
... third week of waiting for MKS support to reply.

was (Author: kovacs00ferenc):
Cletus, I have finally found the root cause... A sub-sub-sub project was messed up somehow by a developer. When trying to open it in Integrity Client, it fatal error-ed back with: "Cannot show view information: Members were added that had already existed". So that's about it.

It is interesting however, that we can checkout and work with all projects with the client GUI except the unimportant broken one, but with the Jenkins plugin, no files can be retrieved. It is also impossible to drop the broken project, since no operation can be performed on it.
... third week of waiting for MKS support to reply.

JIRA noreply@jenkins-ci.org

[JIRA] (JENKINS-13890) FATAL: Unable to retrieve WorkItem data at this point.

In reply to this post by JIRA noreply@jenkins-ci.org

Change By:	Cletus D'Souza (11/Aug/12 3:28 AM)
Status:	Open Closed
Resolution:	Not A Defect

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

JIRA noreply@jenkins-ci.org

[JIRA] (JENKINS-13890) FATAL: Unable to retrieve WorkItem data at this point.

In reply to this post by JIRA noreply@jenkins-ci.org

The plug-in does a viewproject on the whole project. So, if there is a problem somewhere in the tree then the API returns an exception and hence the plug-in cannot proceed.

Will close this issue as there is no problem with the plug-in.