Hello, Since moving to version 1.20 of the integrity plugin (from 1.18), I've noticed that it seems to be detecting SCM changes that don't exist (i.e., it thinks something has changed, when in fact, there have been no changes). The projects are getting built every time the plugin polls MKS for changes.
The polling log shows the following: Polling Log View as plain text <http://m2m-ws3/job/JESS%20--%20Trunk/279/pollingLog/pollingLog> This page captures the polling log that triggered this build. Started on Jan 22, 2014 8:44:20 AM Preparing to execute si projectinfo for #p=c:/path/to/project.pj Preparing to execute si viewproject for #p=c:/path/to/project.pj Project contains changes a total of 6 changes! Done. Took 3.6 sec Changes found Additionally, the build page for each project shows that it was started by an SCM Change, but that there were No Changes for the build: Build #21 (Jan 22, 2014 8:43:17 AM) add description<http://m2m-ws3/job/JESS%20--%20CTS_Phase_2/21/editDescription> Build Artifacts <http://m2m-ws3/job/JESS%20--%20CTS_Phase_2/21/artifact/>No changes. Started by an SCM change<http://m2m-ws3/job/JESS%20--%20CTS_Phase_2/21/pollingLog> Any idea what could be causing this? We are running on Jenkins 1.548. Thanks, Larry -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
