Details
-
Type:
Bug
-
Status: Resolved (View Workflow)
-
Priority:
Blocker
-
Resolution: Fixed
-
Component/s: prqa-plugin
-
Labels:
-
Environment:Jenkins 2.102+
-
Similar Issues:
Description
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.
Attachments
Issue Links
- 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
-
Activity
Field | Original Value | New Value |
---|---|---|
Environment | Jenkins 2.102+ |
Assignee | Praqma Support [ praqma ] | Igor Kostenko [ igorkostenko ] |
Remote Link | This issue links to "Page (Jenkins Wiki)" [ 19818 ] |
Remote Link | This issue links to "Page (Jenkins Wiki)" [ 19818 ] |
Labels | jep-200 | JEP-200 |
Assignee | Igor Kostenko [ igorkostenko ] | Marcos Bento [ marcos_bento ] |
Link |
This issue relates to |
Summary | PRQA Plugin is likely affected by JEP-200 in Jenkins 2.102+ | PRQA Plugin is affected by JEP-200 in Jenkins 2.102+ |
Link |
This issue is duplicated by |
Priority | Minor [ 4 ] | Blocker [ 1 ] |
Status | Open [ 1 ] | In Progress [ 3 ] |
Status | In Progress [ 3 ] | In Review [ 10005 ] |
Resolution | Fixed [ 1 ] | |
Status | In Review [ 10005 ] | Resolved [ 5 ] |
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