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

Maven incremental build doesn't work when changes are in svn:externals

      See: https://issues.jenkins-ci.org/browse/JENKINS-898?focusedCommentId=122278&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-122278
      and
      http://jenkins.361315.n4.nabble.com/JENKINS-898-part-2-svn-externals-and-incremental-build-td4176098.html

      When a change is done in a svn:externals folder, the changelog generated by subversion (changelog.xml) plugin is wrong. As a result the maven plugin is not able to find the changed module.

      Fixing this issue requires to properly generate the SVN changelog, then also fix the maven plugin to handle checkout folder.

          [JENKINS-12127] Maven incremental build doesn't work when changes are in svn:externals

          Julien HENRY added a comment -

          This first patch is for subversion plugin. This is a rework of the changelog builder in order to have a path relative to workspace in all situations (several modules and/or svn:externals)

          Julien HENRY added a comment - This first patch is for subversion plugin. This is a rework of the changelog builder in order to have a path relative to workspace in all situations (several modules and/or svn:externals)

          Julien HENRY added a comment -

          The second patch should be applied on the Maven plugin in order to support changelog paths that are relative to workspace root instead of module root (should have already been the case according to Javadoc). As mentionned in JENKINS-9139, this change may affect other SCM if they are also incorrectly not reporting changes relative to workspace.
          I have not tested complex module paths like ../anotherModule so maybe it would be better to take the patch proposed in JENKINS-9139.

          Julien HENRY added a comment - The second patch should be applied on the Maven plugin in order to support changelog paths that are relative to workspace root instead of module root (should have already been the case according to Javadoc). As mentionned in JENKINS-9139 , this change may affect other SCM if they are also incorrectly not reporting changes relative to workspace. I have not tested complex module paths like ../anotherModule so maybe it would be better to take the patch proposed in JENKINS-9139 .

          Tom A. added a comment -

          I am using hudson and when updating svn view which consists of externals only, every update on subdirectories (from externals) is updated in hudson workspace but changelog says that nothing was modified and the file changelog.xml is wrong (has only "<log/>" string inside) It seems like JENKINS-12127 patch could fix it but ticket is still open and not resolved yet. This is a mustbe functionality for me. Some other plugins depends on changelog for example 'Scan for compiler warnings' will not be launched because of empty changelog.

          Could you tell me if it is going to be delivered?
          Kindly waiting for response.

          Tom A. added a comment - I am using hudson and when updating svn view which consists of externals only, every update on subdirectories (from externals) is updated in hudson workspace but changelog says that nothing was modified and the file changelog.xml is wrong (has only "<log/>" string inside) It seems like JENKINS-12127 patch could fix it but ticket is still open and not resolved yet. This is a mustbe functionality for me. Some other plugins depends on changelog for example 'Scan for compiler warnings' will not be launched because of empty changelog. Could you tell me if it is going to be delivered? Kindly waiting for response.

          kutzi added a comment -

          @Tom A.: you're using Hudson or Jenkins?

          kutzi added a comment - @Tom A.: you're using Hudson or Jenkins?

          Tom A. added a comment -

          I am using Hudson

          Tom A. added a comment - I am using Hudson

          kutzi added a comment -

          So I wonder why you post this question in the Jenkins JIRA instead of the Hudson issue tracker.

          kutzi added a comment - So I wonder why you post this question in the Jenkins JIRA instead of the Hudson issue tracker.

          Tom A. added a comment -

          I have not found similar issue in hudson tracker, I thought fixed plugin could also work for Hudson. The question is why Major Bug is not yet resolved since 2011

          Tom A. added a comment - I have not found similar issue in hudson tracker, I thought fixed plugin could also work for Hudson. The question is why Major Bug is not yet resolved since 2011

          kutzi added a comment -

          Almost all of the current Jenkins plugins won't work with Hudson.

          kutzi added a comment - Almost all of the current Jenkins plugins won't work with Hudson.

            henryju Julien HENRY
            henryju Julien HENRY
            Votes:
            5 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated: