Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-21260

PTC integrity plugin: version 1.19 instantly triggers new build though corresponding files in repository have not been changed!

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Critical Critical
    • integrity-plugin
    • 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!

          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?

          Cletus D'Souza added a comment - 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?

          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.

          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!

          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!

          Grigoriy Milman added a comment - - edited

          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

          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 was a community contributed change that facilitates the Integrity plugin use with the Multiple SCMs plugin.

          Cletus D'Souza added a comment - There was a community contributed change that facilitates the Integrity plugin use with the Multiple SCMs plugin.

          Code changed in jenkins
          User: Cletus D'Souza
          Path:
          src/main/java/hudson/scm/APISession.java
          src/main/java/hudson/scm/IntegrityCMProject.java
          src/main/java/hudson/scm/IntegrityCheckoutTask.java
          src/main/java/hudson/scm/IntegritySCM.java
          http://jenkins-ci.org/commit/integrity-plugin/9c4605abb92d6adebd8618828bd8c49e3d0cb526
          Log:
          Resolved the following issues:
          JENKINS-21587: memory leak in Plugin 1.22 -orphaned Logger Threads (accepted patch from Matthias Rump - thank you!)
          JENKINS-21479: Poll SCM trigger no functioning during the first execution
          JENKINS-21260: PTC integrity plugin: version 1.19 instantly triggers new build though corresponding files in repository have not been changed!

          SCM/JIRA link daemon added a comment - Code changed in jenkins User: Cletus D'Souza Path: src/main/java/hudson/scm/APISession.java src/main/java/hudson/scm/IntegrityCMProject.java src/main/java/hudson/scm/IntegrityCheckoutTask.java src/main/java/hudson/scm/IntegritySCM.java http://jenkins-ci.org/commit/integrity-plugin/9c4605abb92d6adebd8618828bd8c49e3d0cb526 Log: Resolved the following issues: JENKINS-21587 : memory leak in Plugin 1.22 -orphaned Logger Threads (accepted patch from Matthias Rump - thank you!) JENKINS-21479 : Poll SCM trigger no functioning during the first execution JENKINS-21260 : PTC integrity plugin: version 1.19 instantly triggers new build though corresponding files in repository have not been changed!

          This issue is related to Jenkins-21479. This should be resolved now!

          Cletus D'Souza added a comment - This issue is related to Jenkins-21479. This should be resolved now!

          Resolved in 1.23

          Cletus D'Souza added a comment - Resolved in 1.23

            cdsouza Cletus D'Souza
            gremlm Grigoriy Milman
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: