-
Type:
Bug
-
Status: Resolved (View Workflow)
-
Priority:
Blocker
-
Resolution: Fixed
-
Component/s: prqa-plugin
-
Labels:
-
Environment:Jenkins 2.102+
-
Similar Issues:
During the code inspections for JEP-200 I have discovered that the plugin is most likely affected by this security hardening in the Jenkins core.
- Plugin uses PRQAComplianceStatus in MasterToSlaveCallable operations
- This class comes from an external library without a "Jenkins-ClassFilter-Whitelisted" manifest entry
- In Jenkins 2.102+ such classes will be blacklisted unless a workaround is applied
You can find more guidelines for plugin developers in this blogpost: https://jenkins.io/blog/2018/01/13/jep-200/#for-plugin-developers. Please let us know if you need any additional info or reviews regarding this issue.
- is duplicated by
-
JENKINS-50333 While configuring PRQA Post build action error is coming
-
- Resolved
-
- relates to
-
JENKINS-50333 While configuring PRQA Post build action error is coming
-
- Resolved
-
I have got information from Ewelina Wilkosz that the plugin is no longer maintained by Praqma.
CC Igor Kostenko and Marcos Bento who are listed in Repository permission updater