Some additional information: The Jenkins instance where the problem occurs, uses java-11-openjdk-11.0.21.0.9-1.el7_9.x86_64/bin/java as JRE, and runs in RHEL7 3.10.0-1160.102.1.el7.x86_64 while the instance where I do not have the problem uses java-17-openjdk-17.0.9.0.9-2.el8.x86_64 and runs on RHEL8 4.18.0-477.27.1.el8_8.x86_64

Both instances share the same source code and project specifications and produce identical results.

The difference is that one is TEST (the one that works) and one is PROD.

Since RHEL7 officially is no longer supportedby Jenkins, this may not be an issue anymore.

Hi d_altemyr 

So I think once you upgrade PROD to java 17, and maybe upgrade jenkins and plug-ins (if not matching TEST already), the issue should disappear. At least in theory.

Do you think there's anything left to do here for now? I do not mind leaving the issue open until you can try that. Just remember to let us know whether that worked or not

Cheers

I'm beginning to suspect that there is something else with my project that causes this problem. I have recently upgraded the system to be using java 17 in both environments. The PROD is still in RHEL7 and there is no chance that it will be upgraded to RHEL8. After upgrading to Jenkins version 2.442 last week, the problem occurs in both environments, with the same log info as before.

org.apache.commons.jelly.JellyTagException: jar:file:/var/opt/jenkins/skvzv/plugins/tap/WEB-INF/lib/tap.jar!/org/tap4j/plugin/TapResult/index.jelly:12:57: <st:include> No page found 'sidepanel.jelly' for class org.tap4j.plugin.TapResult

However, I let those projects archive the *.tap.result files and created a new project that is triggered by the first, and its only action is to import the *.tap.result files from the original project and publich that tap result, and in that project the TAP Extended Test Results does functions as it should.

We're seeing the same "sidepanel.jelly" issue.
Jenkins 2.426.3
TAP 2.4.1
Ubuntu 22.0.4
OpenJDK 11.0.21+9
Both in the original build as well as copying the result files into a parent pipeline. Seems it may be intermittent. Some users report it sometimes works in the parent job but not the child (orignal) job.

Related: https://issues.jenkins.io/browse/JENKINS-72561

with fix: https://github.com/jenkinsci/testlink-plugin/pull/35/files#diff-31dd1abd06977c0970dbe941fa47ab24c0cec3967cb7be76b5f82013479ff0ea

Thanks for the links, Victor!

Couldn't reproduce it, but I think rudometov 's suggestion is really good. Will implement a similar approach for tap-plugin.

Pending some testing now, but here's a PR for that: https://github.com/jenkinsci/tap-plugin/pull/40/files

d_altemyr it'd be really great if you had a way to test that branch too, as I was not able to reproduce the error.

Released in 2.4.3. Should be available in the update site in the next minutes/hours. Let me know if that fixed the issue for those that had the sidepanel.jelly. Feel free to re-open if the issue occurs again.

I've checked and 2.4.3 fixes the issue for my setup. Thanks!