-
Bug
-
Resolution: Fixed
-
Critical
-
None
-
Windows 7
After upgrading from PTC integrity plugin from 1.18 to 1.19, build job is instantly triggered each time when polling SCM changes is scheduled, though there were no changes in repository!
PTC plugin version 1.18 doesn't have such "feature"
[JENKINS-21260] PTC integrity plugin: version 1.19 instantly triggers new build though corresponding files in repository have not been changed!
Grigoriy Milman
created issue -
Grigoriy Milman
made changes -
| Summary | Original: PTC integrity plugin: version 1.9 does not | New: PTC integrity plugin: version 1.9 instantly triggers new build though corresponding files in repository have not been changed! |
Grigoriy Milman
added a comment - Due to this issue we have already roll back to 1.8 version of the plugin.
There are more than 100 build jobs in our system, and instant rebuild of them was really annoying.
In any way, we can't afford to re-create all jobs.
Grigoriy Milman
added a comment -
Due to this issue we have already roll back to 1.8 version of the plugin.
There are more than 100 build jobs in our system, and instant rebuild of them was really annoying.
In any way, we can't afford to re-create all jobs. There were come configuration changes made in v1.19 that has changed the default location for the embedded Derby database. Can you delete your Job and re-create it to see if that resolves the polling issue?
With PTC plugin v1.20 I have disabled the current build job and create then new one based on the config of disabled and started build of new job manually.
After that new job was started by an SCM change after each polling interval again, the same as original job.
Polling log shows
Polling Log
This page captures the polling log that triggered this build.
Started on Jan 10, 2014 5:06:37 PM
Preparing to execute si projectinfo for /repository/CorporateMeasurementTechnologies/SWProduction/Tools/BuildProcess/JenkinsMSEI/GetBuildResults/project.pj
Preparing to execute si viewproject for /repository/CorporateMeasurementTechnologies/SWProduction/Tools/BuildProcess/JenkinsMSEI/GetBuildResults/project.pj
Project contains changes a total of 59 changes!
Done. Took 39 sec
Changes found
By the way, it is not clear what that 59 changes are! It is not file changes!
Grigoriy Milman
added a comment - - edited
There were come configuration changes made in v1.19 that has changed the default location for the embedded Derby database. Can you delete your Job and re-create it to see if that resolves the polling issue?
With PTC plugin v1.20 I have disabled the current build job and create then new one based on the config of disabled and started build of new job manually.
After that new job was started by an SCM change after each polling interval again, the same as original job.
Polling log shows
Polling Log
This page captures the polling log that triggered this build.
Started on Jan 10, 2014 5:06:37 PM
Preparing to execute si projectinfo for /repository/CorporateMeasurementTechnologies/SWProduction/Tools/BuildProcess/JenkinsMSEI/GetBuildResults/project.pj
Preparing to execute si viewproject for /repository/CorporateMeasurementTechnologies/SWProduction/Tools/BuildProcess/JenkinsMSEI/GetBuildResults/project.pj
Project contains changes a total of 59 changes!
Done. Took 39 sec
Changes found
By the way, it is not clear what that 59 changes are! It is not file changes! The zip file contains directory related to the new build jobs
Grigoriy Milman
added a comment - - edited The zip file contains directory related to the new build jobs Grigoriy Milman
made changes -
| Attachment | New: TOOLS.BUILD-JenkinsMSEI.GetBuildResults_TEST.zip [ 24988 ] |
Grigoriy Milman
made changes -
| Description |
Original:
After upgrading from PTC integrity plugin from 1.8 to 1.9, build job is instantly triggered each time when polling SCM changes is scheduled, though there were no changes in repository! PTC plugin version 1.8 doesn't have such "feature" |
New:
After upgrading from PTC integrity plugin from 1.18 to 1.19, build job is instantly triggered each time when polling SCM changes is scheduled, though there were no changes in repository! PTC plugin version 1.18 doesn't have such "feature" |
Grigoriy Milman
made changes -
| Summary | Original: PTC integrity plugin: version 1.9 instantly triggers new build though corresponding files in repository have not been changed! | New: PTC integrity plugin: version 1.19 instantly triggers new build though corresponding files in repository have not been changed! |
Grigoriy Milman
added a comment - From JENKINS-20767, which is the same issue but related to the GIT plugin:
...
Other observation: We use the multiple SCMs plugin. Which is known to be problematic. In this case the issue is not isolated to jobs that use that plugin. All jobs are affected.
PTC plugin now is using multiple SCMs plugin?
Grigoriy Milman
added a comment - From JENKINS-20767 , which is the same issue but related to the GIT plugin:
...
Other observation: We use the multiple SCMs plugin. Which is known to be problematic. In this case the issue is not isolated to jobs that use that plugin. All jobs are affected.
PTC plugin now is using multiple SCMs plugin? 
There were come configuration changes made in v1.19 that has changed the default location for the embedded Derby database. Can you delete your Job and re-create it to see if that resolves the polling issue?