jenkins2 Perform release error svn: E230001
Bonjour
J'ai l'erreur suivante sous Jenkins2 uniquement lorsque je souhaite effectuer uniquement une perform-release, pas de soucis lors d'une compilation normal.
l'erreur est
Code:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
|
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. |
j'ai esssayé depuis la machine ou est installé jenkins la manipulation suivante SANS SUCCES
- supprimer le répertoire "Subversion/auth" afin que la question me soit posée ou j'ai répondu p
- creer un bat comme ci dessous, afin de pouvoir valider le certificat,
- La commande "svn list" passe sans problème, mais pas ensuite le perform-release sous jenkins2 ??
- puis j'ai redemarré jenkins ! cela ne fonctionne pas
Code:
1
2
|
svn list https://zz.com:8443/svn/XXX/YYY/trunk |
Les arguments dans Jenkins2 pour le perform sont
Code:
1
2
3
|
Release goals and options : -Dresume=false release:prepare release:perform
DryRun goals and options: -Dresume=false -DdryRun=true release:prepare |
Le pom du projet
Code:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
|
<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> |
La machine ou est Jenkins2 est un serveur Windows2012 avec le client tortoise SVN 1.9.3.
N'y aurait t'il pas un client svn intégré à Jenkins et n'utilisant pas le client tortoise, et donc ayant besoin de la validation du certificat ?
Mon utilisateur sous Visual SVN Server sur le serveur zz.com possède les droits en lecture/écriture
Pourquoi un Build normal passe ???
Merci de votre aide
Phil
