Bug 513951 - Signing service is down
Summary: Signing service is down
Status: CLOSED DUPLICATE of bug 513954
Alias: None
Product: Community
Classification: Eclipse Foundation
Component: Servers (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows NT
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Eclipse Webmaster CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-03-20 17:40 EDT by Pascal Rapicault CLA
Modified: 2017-03-21 10:24 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Pascal Rapicault CLA 2017-03-20 17:40:50 EDT
The signing service seems to be down.
I got the following failure on EGerrit builds: https://hudson.eclipse.org/egerrit/job/EGerrit/866/


17:38:05  [DEBUG] Closing connection to remote
17:38:05  [ERROR] Failed to execute goal org.eclipse.cbi.maven.plugins:eclipse-jarsigner-plugin:1.1.0:sign (sign) on project org.eclipse.egerrit.model: Failed to sign file. -> [Help 1]
17:38:05  org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.eclipse.cbi.maven.plugins:eclipse-jarsigner-plugin:1.1.0:sign (sign) on project org.eclipse.egerrit.model: Failed to sign file.
17:38:05  	at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)
17:38:05  	at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
17:38:05  	at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
17:38:05  	at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
17:38:05  	at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
17:38:05  	at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
17:38:05  	at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
17:38:05  	at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)
17:38:05  	at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)
17:38:05  	at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)
17:38:05  	at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863)
17:38:05  	at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)
17:38:05  	at org.apache.maven.cli.MavenCli.main(MavenCli.java:199)
17:38:05  	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
17:38:05  	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
17:38:05  	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
17:38:05  	at java.lang.reflect.Method.invoke(Method.java:498)
17:38:05  	at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
17:38:05  	at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
17:38:05  	at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
17:38:05  	at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
17:38:05  Caused by: org.apache.maven.plugin.MojoExecutionException: Failed to sign file.
17:38:05  	at org.eclipse.cbi.maven.plugins.jarsigner.SignMojo.signFile(SignMojo.java:364)
17:38:05  	at org.eclipse.cbi.maven.plugins.jarsigner.SignMojo.signArtifact(SignMojo.java:262)
17:38:05  	at org.eclipse.cbi.maven.plugins.jarsigner.SignMojo.execute(SignMojo.java:195)
17:38:05  	at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
17:38:05  	at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207)
17:38:05  	... 20 more
Comment 1 Frederic Gurr CLA 2017-03-21 07:34:09 EDT

*** This bug has been marked as a duplicate of bug 513954 ***
Comment 2 Frederic Gurr CLA 2017-03-21 10:24:25 EDT
This was caused by an DNS issue and should be fixed now (see bug 513954 comment 5).