• Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • vss-plugin
    • None
    • Jenkins ver. 1.426 with VSS-Plugin ver. 1.9

      Since VSS-Plugin version 1.9 my incremental build doesn't work anymore. I have a job that is triggered by SCM update. Even if there's no change in VSS repository, I get the following message:
      [poll] No previous build, so forcing an initial build.
      There are previous builds.

      I think the bug is caused by this code in compareRemoteRevisionWith():

      //If this is the build then it deserves a build.
      AbstractBuild<?, ?> lastBuild = (AbstractBuild<?,?>)project.getLastBuild();
      if(lastBuild == null)

      { tl.getLogger().println("[poll] Last Build : #" + lastBuild.getNumber()); }

      else

      { // If we've never built before, well, gotta build! tl.getLogger().println("[poll] No previous build, so forcing an initial build."); return PollingResult.BUILD_NOW; }

      The logic of the "if" statement should be the other way round; when lastBuild is null, one couldn't call getNumber() without an exception.

          [JENKINS-10730] VSS-Plugin incremental build broken

          rioch added a comment -

          Thanks for the report. I'll take a look at this as soon as possible. I'm quite busy at the moment so it may be a couple of weeks.

          rioch added a comment - Thanks for the report. I'll take a look at this as soon as possible. I'm quite busy at the moment so it may be a couple of weeks.

          Michael Fink added a comment -

          I prepared a patch for vss-plugin with a cloned git repository from github. I verified that with this patch the incremental build works again. If you look at the code, you see that the logic of the if()-expression is just backwards.

          Michael Fink added a comment - I prepared a patch for vss-plugin with a cloned git repository from github. I verified that with this patch the incremental build works again. If you look at the code, you see that the logic of the if()-expression is just backwards.

          Mark Madine added a comment -

          Are there any more updates on this?

          Mark Madine added a comment - Are there any more updates on this?

          Michael Fink added a comment -

          Unfortunately not. The attached patch fixes the specific problem, but there's no new version of the VSS-Plugin, and there seems to be at least another memory leak somewhere. Best to migrate to an other SCM...

          Michael Fink added a comment - Unfortunately not. The attached patch fixes the specific problem, but there's no new version of the VSS-Plugin, and there seems to be at least another memory leak somewhere. Best to migrate to an other SCM...

          Would there be an update in nearer future? I have updatet to the current Version and since then I have this problem.
          How can I use the patch?

          Jens Hirschfeld added a comment - Would there be an update in nearer future? I have updatet to the current Version and since then I have this problem. How can I use the patch?

          Mark Madine added a comment - - edited

          We have started moving to SVN (thankfully).
          We still use VSS, I patched the plugin locally.

          Pull the source from: https://github.com/jenkinsci/vss-plugin
          Apply the patch and build the plugin with Maven.

          Mark Madine added a comment - - edited We have started moving to SVN (thankfully). We still use VSS, I patched the plugin locally. Pull the source from: https://github.com/jenkinsci/vss-plugin Apply the patch and build the plugin with Maven.

            Unassigned Unassigned
            vividos Michael Fink
            Votes:
            2 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: