Details
-
Bug
-
Status: Fixed but Unreleased (View Workflow)
-
Major
-
Resolution: Fixed
-
None
-
TestLink(1.9.20)
Jenkins(2.261)
TestLink plugin(3.16)
Linux
Description
| 1. In TestLink(1.9.20) I have created a test plan, Requirements, Testcases, Custom fields and associated automation scripts to the test cases. 2. In Jenkins(2.261) downloaded TestLink plugin(3.16) and made all the needed configurations like in "Configuration", in TestLink section I have given name to TestLink, URL of xmlrpc.php and Developer Key generated from TestLink. 3. Created a jenkins job and when I run it, I get TestNG reports, but getting TestLink reports as "Not Run". 4. When I click on TestLink results, it gives me the below error. org.apache.commons.jelly.JellyTagException: jar:file:/var/lib/jenkins/plugins/testlink/WEB-INF/lib/testlink.jar!/hudson/plugins/testlink/TestLinkResult/index.jelly:6:57: No page found 'sidepanel.jelly' for class hudson.plugins.testlink.TestLinkResult |
Attachments
Issue Links
- duplicates
-
-
- Fixed but Unreleased
-
-
-
- Fixed but Unreleased
-
-
-
- Fixed but Unreleased
-
-
-
- Fixed but Unreleased
-
-
-
- Fixed but Unreleased
-
Activity
| Field | Original Value | New Value |
|---|---|---|
| Attachment | image-2020-11-03-20-31-58-154.png [ 53209 ] |
Hi lvaranasi
There is a fix here: https://github.com/jenkinsci/testlink-plugin/pull/35
There were some changes regarding how objects were persisted after a build. The Jenkins internal code also changed a little, in a way that the objects persisted are not always there.
The plug-in was basically trying to load sidepanel.jelly from the Run (an execution of the job, aka a build/etc). But since the Run was not persisted, it failed to load the sidepanel.jelly file.
The pull request fixes it, as it's possible to see in this screenshot.
The plug-in, however, needs more work before it's ready for a release. There are other parts of the code that are using deprecated API, the minimum version needs to be bumped up to the latest LTS release, more code can be removed (I threw away some code already in the PR), and, more importantly, I think we need to use the credentials plug-in for the XMLRPC API, to comply with the security best practices.
As I am not using Jenkins, and not using TestLink, I can't use my time from $work to work on this. And on my spare time I have a few other projects I'm either using or being sponsored that I need to fix first.
If you know some Java, and you can help with pull requests, I'd be happy to review/merge, until we get ready for a release. Otherwise, I will have long vacations in December, and *may* be able to cut a new release with a revamped version of the plug-in, compatible with the latest TestLink.
Cheers
Bruno
p.s. *may* because December is also summer where I live, and we have-so far-no lockdown over here, so I might be out of the city or spending time with family; but again, reviewing PR's takes only some minutes, or maybe one or two hours, which I can always squeeze in, and any Jenkins core/maintainer can release the plug-in, so that I don't bottleneck the process
| Link |
This issue duplicates |
| Link |
This issue duplicates |
| Link |
This issue duplicates |
| Link |
This issue duplicates |
| Link |
This issue duplicates |
| Resolution | Fixed [ 1 ] | |
| Status | Open [ 1 ] | Fixed but Unreleased [ 10203 ] |
Hi Bruno, any updates on this issue?