Details
-
Type:
Bug
-
Status: Closed (View Workflow)
-
Priority:
Minor
-
Resolution: Fixed
-
Component/s: delivery-pipeline-plugin
-
Labels:
-
Environment:* delivery-pipeline-plugin 0.9.5
* Jenkins ver. 1.609.2
-
Similar Issues:
Description
This issue relates to JENKINS-30018
Two things:
1) In our case someone added third regular expression input field to Pipelines section, left it completely empty and saved the configuration. As a result our jenkins.log started to grow rapidly.
Aug 18, 2015 10:42:38 AM se.diabol.jenkins.pipeline.util.ProjectUtil getProjects WARNING: Could not find match group
Above output 1223 times per second and now our jenkins.log is counted in tens of gigs. The spamming stopped when the empty field was removed.
It should not be possible to leave regular expression input field blank, but it should be removed when view configuration is saved.
2) Is it really necessary call getProjects function that often?
Attachments
Activity
Pull request merged: https://github.com/Diabol/delivery-pipeline-plugin/pull/242
Will be part of next release.
Tommy Tynjä
added a comment - Pull request merged: https://github.com/Diabol/delivery-pipeline-plugin/pull/242
Will be part of next release. Released in Delivery Pipeline plugin 1.0.2.
Tommy Tynjä
added a comment - Released in Delivery Pipeline plugin 1.0.2. 
I was not able to reproduce this with a blank regexp value in the configuration. Teemu Suvanto could you please test with the latest released version (0.10.2) to see if the problem persist? In such case, could you please provide the value of the regexp configuration as well as the relevant job configuration so that we can reproduce the behavior?
I agree that it would be feasible to validate the input not being blank.