-
Notifications
You must be signed in to change notification settings - Fork 98
Add property for detection of inline javascript #814
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
Add property `jelly.requireNoInlineJS`. This is passed to the injected tests as parameters. When jenkinsci/jenkins-test-harness#868 gets merged this will b enable the checks. By default the checks are enabled. At a later point in time we might consider removing this property so that it is no longer possible to disable the check. Or we might ignore it when the Jenkins core version is higher than a certain version.
src/main/java/org/jenkinsci/maven/plugins/hpi/TestInsertionMojo.java
Outdated
Show resolved
Hide resolved
src/main/java/org/jenkinsci/maven/plugins/hpi/TestInsertionMojo.java
Outdated
Show resolved
Hide resolved
daniel-beck
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Unsure how long this is going to be relevant though given the hpi:run default behavior in 2.539+.
Noting jenkinsci/jenkins-test-harness#868 (review).
Also, if the println refactor was done mechanically, it'd have been nice in a separate(ly ignorable) commit.
NotMyFault
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Untested, but code looks reasonable.
Add property
jelly.prohibitInlineJS. This is passed to the injected tests as parameters.When jenkinsci/jenkins-test-harness#868 gets merged this will enable the checks.
By default the checks are enabled here.
At a later point in time we might consider removing this property so that it is no longer possible to disable the check. Or we might ignore it when the Jenkins core version is higher than a certain version.
Testing done
Tested that in combination with jenkinsci/jenkins-test-harness#868 setting the property to false will not trigger the check.
Submitter checklist