Skip to content

Conversation

@mawinter69
Copy link

@mawinter69 mawinter69 commented Nov 16, 2025

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

  • Make sure you are opening from a topic/feature/bugfix branch (right side) and not your main branch!
  • Ensure that the pull request title represents the desired changelog entry
  • Please describe what you did
  • Link to relevant issues in GitHub or Jira
  • Link to relevant pull requests, esp. upstream and downstream changes
  • Ensure you have provided tests that demonstrate the feature works or the issue is fixed

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.
Copy link
Member

@daniel-beck daniel-beck left a 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.

Copy link
Member

@NotMyFault NotMyFault left a 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants