Skip to content

Conversation

@tiago-espinha-img
Copy link
Contributor

Automatic test file validation causes issues when workspaces have large O(millions) amount of files. In those cases, if the particular test file doesn't exist at the time the user looks at the configuration page, the Agent will start crawling the whole workspace looking for other subdirectories where that file might be.

By doing so, it's tracking all the files it's seen which eventually leads to filling up the heap and crashing.

This disables the automatic file validation and adds a button that makes it possible to validate manually.

Testing done

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

Automatic test file validation causes issues when workspaces have
large O(millions) amount of files. In those cases, if the particular
test file doesn't exist at the time the user looks at the
configuration page, the Agent will start crawling the whole workspace
looking for other subdirectories where that file might be.

By doing so, it's tracking all the files it's seen which eventually
leads to filling up the heap and crashing.

This disables the automatic file validation and adds a button that
makes it possible to validate manually.
* @throws IOException if an error occurs.
*/
public FormValidation doCheckTestResults(@AncestorInPath AbstractProject project, @QueryParameter String value)
public FormValidation doValidateTestResults(

Check warning

Code scanning / Jenkins Security Scan

Stapler: Missing POST/RequirePOST annotation Warning

Potential CSRF vulnerability: If DescriptorImpl#doValidateTestResults connects to user-specified URLs, modifies state, or is expensive to run, it should be annotated with @POST or @RequirePOST
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.

1 participant