jenkins2 Perform release error svn: E230001

139 views
Skip to first unread message

Philippe Couas

unread,
Nov 8, 2016, 4:03:22 PM11/8/16
to Jenkins Users
Hi,

I have following error message on jenkins2 only when i made an perform-release, no problem on build.

l'erreur est
[code]
Command output:
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-release-plugin:2.5.2:prepare (default-cli) on project YYY: Unable to commit files
[ERROR] Provider message:
[ERROR] The svn command failed.
[ERROR] Command output:
svn: E170013: Commit failed (details follow):
svn: E170013: Unable to connect to a repository at URL 'https://zz.com:8443/svn/XXX/YYY/trunk'
svn: E230001: Server SSL certificate verification failed: certificate issued for a different hostname, issuer is not trusted


    at org.apache.maven.shared.release.phase.AbstractScmCommitPhase.checkin(AbstractScmCommitPhase.java:165)
    at org.apache.maven.shared.release.phase.AbstractScmCommitPhase.performCheckins(AbstractScmCommitPhase.java:145)
    at org.apache.maven.shared.release.phase.ScmCommitPreparationPhase.runLogic(ScmCommitPreparationPhase.java:76)
    at org.apache.maven.shared.release.phase.AbstractScmCommitPhase.execute(AbstractScmCommitPhase.java:78)
    at org.apache.maven.shared.release.DefaultReleaseManager.prepare(DefaultReleaseManager.java:234)
    at org.apache.maven.shared.release.DefaultReleaseManager.prepare(DefaultReleaseManager.java:169)
    at org.apache.maven.shared.release.DefaultReleaseManager.prepare(DefaultReleaseManager.java:146)
    at org.apache.maven.shared.release.DefaultReleaseManager.prepare(DefaultReleaseManager.java:107)
    at org.apache.maven.plugins.release.PrepareReleaseMojo.prepareRelease(PrepareReleaseMojo.java:286)

org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-release-plugin:2.5.2:prepare (default-cli) on project YYY: Unable to commit files
Provider message:
The svn command failed.


[/code]
I have tried without succes
- 1 delete directory "Subversion/auth" p
- 2 command "svn list" without problem, but NOT perform-release jenkins2 ??
[code]
svn list https://zz.com:8443/svn/XXX/YYY/trunk
[/code]

On Jenkins2 perform command :
[code]
Release goals and options : -Dresume=false release:prepare release:perform
DryRun goals and options: -Dresume=false -DdryRun=true release:prepare
[/code]

POM
[code]
<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
    <modelVersion>4.0.0</modelVersion>
    <groupId>fr.toto.receive</groupId>
    <artifactId>receiveMail</artifactId>
    <packaging>jar</packaging>
    <name>receive</name>
    <version>1.0.0-SNAPSHOT</version>
    <description>Reception Email</description>

   <scm>
        <connection>scm:svn:https://zz.com:8443/svn/XXX/YYY/trunk</connection>
        <developerConnection>scm:svn:https://zz.com:8443/svn/XXX/YYY/trunk</developerConnection>
          <url>https://zz.com:8443/svn/XXX/YYY/trunk</url>
    </scm>

        <properties>
        <src.dir>src</src.dir>
    </properties>

    <build>
        <sourceDirectory>${src.dir}</sourceDirectory>
   
        <plugins>
            <plugin>
                <groupId>org.apache.maven.plugins</groupId>
                <artifactId>maven-compiler-plugin</artifactId>
                <version>3.6.0</version>
                <configuration>
                    <source>1.7</source>
                    <target>1.7</target>
                </configuration>
            </plugin>
            <plugin>
                <groupId>org.apache.maven.plugins</groupId>
                <artifactId>maven-jar-plugin</artifactId>
                <version>3.0.2</version>
                <configuration>
                    <finalName>ReceiveMail</finalName>                  
                </configuration>
            </plugin>   

        </plugins>
        <pluginManagement>
        <plugins>
            <plugin>
                  <artifactId>maven-release-plugin</artifactId>
                <version>2.5.2</version>
               </plugin>
              <plugin>
                <groupId>org.sonarsource.scanner.maven</groupId>
                <artifactId>sonar-maven-plugin</artifactId>
                <version>3.1.1</version>
              </plugin>
        </plugins>
          </pluginManagement>
    </build>
    <dependencies>
        <dependency>
            <groupId>org.apache.maven.plugins</groupId>
            <artifactId>maven-clean-plugin</artifactId>
            <version>3.0.0</version>
        </dependency>
        <dependency>
            <groupId>javax.activation</groupId>
            <artifactId>activation</artifactId>
            <version>1.1.1</version>
            <type>jar</type>        
            <scope>provided</scope>
        </dependency>
        <dependency>
            <groupId>commons-codec</groupId>
            <artifactId>commons-codec</artifactId>
            <version>1.8</version>
            <type>jar</type>        
            <scope>provided</scope>
        </dependency>
        <dependency>
               <groupId>dnsjava</groupId>
            <artifactId>dnsjava</artifactId>
               <version>2.1.1</version>
               <type>jar</type>        
            <scope>provided</scope>
        </dependency>
        <dependency>
               <groupId>net.sourceforge.htmlcleaner</groupId>
            <artifactId>htmlcleaner</artifactId>
            <version>2.10</version>
            <type>jar</type>        
            <scope>provided</scope>
        </dependency>
        <dependency>
            <groupId>javax.mail</groupId>
            <artifactId>mail</artifactId>
            <version>1.4</version>
        </dependency>
        <!-- Oracle11 -->
        <dependency>
            <groupId>com.oracle</groupId>
            <artifactId>ojdbc5</artifactId>
            <version>11.2.0.2.0</version>
            <type>jar</type>        
            <scope>provided</scope>
        </dependency>
    </dependencies>
</project>
[/code]

Computer with Jenkins2 is Windows2012 with tortoise SVN 1.9.3 ?S
My remote user on VisualSVN server, could read and write
Why build is Ok ?
Where is my mistake ?

Regards

Phil

Nicolas M

unread,
Nov 16, 2016, 8:02:42 AM11/16/16
to Jenkins Users
Hi,

I think that you must accept the certificate permanently by running an svn command-line client.
Under Windows, you might have to copy paste the files generated in C:\Users\yourUser\AppData\Roaming\Subversion\auth to the directory of the user running Jenkins.
By default, Jenkins runs with the system user (C:\Windows\System32\config\systemprofile\AppData\Roaming\Subversion\auth)
Reply all
Reply to author
Forward
0 new messages