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

Release build fails on jenkins-slave for MultiModuleMavenProjects

    Details

    • Type: Bug
    • Status: Open (View Workflow)
    • Priority: Critical
    • Resolution: Unresolved
    • Component/s: m2release-plugin
    • Environment:
      Jenkins 1.525, 1.530, Windows 2008 R2, (and Win 7 also), SVN 1.5 (Server), Svnkit (Client)
    • Similar Issues:

      Description

      Releasing a MultiModuleMavenProject on a jenkins-slave via m2release-plugin always fails:

      [INFO] Checking in modified POMs...
      .
      svn: E155004: Working copy 'C:\JenkinsDATA\workspace\MavenDemoDeploy' locked; try performing 'cleanup'

      If I make the initial checkout and maven release build on command-line of the slave-machine everything works fine. If I make the release build on jenkins-slave for a single maven module everything works fine. If I make the release build for the multi maven module on the master everything works fine.

      I configured the release-plugin to use the svnkit, so it is the same client as jenkins use to checkout. I also configured preparationGoals to make a 'svn cleanup' (the cleanup works) without any success.

        Attachments

          Activity

          Hide
          michael_k Michael Kopf added a comment -

          I have found a workaround. I have configured the property commitByProject for the release-plugin. That solves the problem. But in my opinion here is still a bug in jenkins and it should work without this parameter also.

          Show
          michael_k Michael Kopf added a comment - I have found a workaround. I have configured the property commitByProject for the release-plugin. That solves the problem. But in my opinion here is still a bug in jenkins and it should work without this parameter also.
          Hide
          djeanprost Dominique Jean-Prost added a comment -

          The problem appears on a single node jenkins installation too.

          Show
          djeanprost Dominique Jean-Prost added a comment - The problem appears on a single node jenkins installation too.
          Hide
          jamesdumay James Dumay added a comment -

          Looking at the description it appears the problem is how the m2release plugin uses the subversion plugin (not the other way around). Ive removed the subversion-plugin component from this issue.

          Show
          jamesdumay James Dumay added a comment - Looking at the description it appears the problem is how the m2release plugin uses the subversion plugin (not the other way around). Ive removed the subversion-plugin component from this issue.

            People

            • Assignee:
              Unassigned
              Reporter:
              michael_k Michael Kopf
            • Votes:
              3 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

              • Created:
                Updated: