-
New Feature
-
Resolution: Unresolved
-
Minor
We would like to request for an option to disable warning plugin's parsing and displaying of project source code (source code view feature); ideally having the ability to set it at instance/master level as well as project's parser level.
For very large project where we are more interest in tracking metric, we found this parse/displaying to be expensive on storage; in addition we notice view content permission is tied to job read permission (more open in our instance), instead workspace permission (limited to admin) - in our env with mix-ed repo with diff permission level but builds together, this can potentially exposes source code when we want intended to share build result/console output.
- is related to
-
JENKINS-72544 hide source code if user does not have access to workspace
-
- Open
-
- relates to
-
JENKINS-58167 Add option to not store affected files
-
- Resolved
-
-
JENKINS-62151 Add option to compress affected files
-
- Resolved
-
[JENKINS-61038] Add permissions for source code viewer
Assignee | Original: Ulli Hafner [ drulli ] | |
Labels | New: help-wanted |
Link |
New:
This issue relates to |
Epic Link |
New:
|
Summary | Original: Ability to disable source code view at master and/or project level | New: Add option to disable source code persistence |
Summary | Original: Add option to disable source code persistence | New: Add permissions for source code viewer |
That makes sense to look into at a higher level. As already discussed with the coverage-api team it would make sense to extract the source code rendering into a new plugin that has all those features in a single place.