-
Bug
-
Resolution: Unresolved
-
Major
-
Jenkins 1.651
URL Trigger plugin 0.41
When the polling schedule is changed the plugin forgets the results of the previous poll even if the URL response check configuration is unchanged. This means for example on a 24 hour polling period it would actually take 48 hours to register a change.
The desired behaviour would be:
1. Allow updates to the polling schedule without affecting previously collected results
or
2. Allow a method of manually capturing the URL response state prior to a poll taking place.
[JENKINS-33740] Plugin forgets previous poll result when polling schedule is changed
Dana Goyette
added a comment - It looks more like it forgets the previous poll result when ANY configuration field of the job is changed.
It looks like the retrieved data isn't saved to disk anywhere, and is forgotten when the job is reloaded.
From JSONContentType.java:
private transient Map<String, Object> results = null;
I'm not too familiar with the Jenkins plugin code, but maybe only non-transient fields are actually stored to disk?
Dana Goyette
added a comment - It looks more like it forgets the previous poll result when ANY configuration field of the job is changed.
It looks like the retrieved data isn't saved to disk anywhere , and is forgotten when the job is reloaded.
From JSONContentType.java:
private transient Map<String, Object> results = null;
I'm not too familiar with the Jenkins plugin code, but maybe only non-transient fields are actually stored to disk? 
Is there any plan or hot fix for this issue?
thanks.