Community
Participate
Working Groups
I noticed that in recent Linux Tools builds such as this one: https://hudson.eclipse.org/hudson/job/cbi-linuxtools-Indigo/336/console The p2 repository is failing to be created: [INFO] Building zip: /opt/users/hudsonbuild/workspace/cbi-linuxtools-Indigo/releng/org.eclipse.linuxtools.releng-site/target/packed/org.eclipse.linuxtools.releng-site.zip-after-removing.zip [ERROR] java.io.FileNotFoundException: /home/data/httpd/download-staging.priv/technology/linuxtools/d76dc725-e464-4b97-892e-f18cb5f024e3/org.eclipse.linuxtools.releng-site.zip (No such file or directory) at java.io.FileOutputStream.open(Native Method) at java.io.FileOutputStream.<init>(FileOutputStream.java:179) at java.io.FileOutputStream.<init>(FileOutputStream.java:131) at org.codehaus.plexus.util.FileUtils.copyFile(FileUtils.java:930) at org.eclipse.dash.m4e.eclipse.signing.SignMojo.signLocally(SignMojo.java:189) at org.eclipse.dash.m4e.eclipse.signing.SignMojo.execute(SignMojo.java:167) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59) at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:319) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156) at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196) at org.apache.maven.cli.MavenCli.main(MavenCli.java:141) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409) at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352) There's also this stack trace: ERROR] Failed to execute goal org.eclipse.dash.maven:eclipse-maven-signing-plugin:1.0.1.0-SNAPSHOT:pack (repack) on project org.eclipse.linuxtools.releng-site: file to pack does not exist! -> /opt/users/hudsonbuild/workspace/cbi-linuxtools-Indigo/releng/org.eclipse.linuxtools.releng-site/target/signed/site_assembly.zip -> [Help 1] org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.eclipse.dash.maven:eclipse-maven-signing-plugin:1.0.1.0-SNAPSHOT:pack (repack) on project org.eclipse.linuxtools.releng-site: file to pack does not exist! -> /opt/users/hudsonbuild/workspace/cbi-linuxtools-Indigo/releng/org.eclipse.linuxtools.releng-site/target/signed/site_assembly.zip at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:213) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59) at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:319) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156) at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196) at org.apache.maven.cli.MavenCli.main(MavenCli.java:141) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409) at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352) Caused by: org.apache.maven.plugin.MojoFailureException: file to pack does not exist! -> /opt/users/hudsonbuild/workspace/cbi-linuxtools-Indigo/releng/org.eclipse.linuxtools.releng-site/target/signed/site_assembly.zip at org.eclipse.dash.m4e.eclipse.signing.PackMojo.execute(PackMojo.java:111) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209) ... 19 more
FWIW nothing has changed in our releng directory or our top-level or releng pom.xml files since our successful signed builds last week.
Something seems to have changed with the signing infrastructure and Hudson. Nothing has changed in the Dash maven signing plugin and nothing has changed in Linux Tools' releng settings yet the signing now fails. The best guess we have is from Dave Carver: d_a_carver: overholt, at this point it looks like the signing process isn't returning the zip, or doesn't have permissions to write to that directory. They might need to rerun ACL. Does this ring a bell, webmasters? I wish I had more precise information but unfortunately I do not.
This just happened again as can be seen in this log: https://hudson.eclipse.org/hudson/job/cbi-linuxtools-Indigo/343/console
I think the issue was a missing ACL on technology/linuxtools. Please try your signing again. -M.
Thanks, Matt! That does appear to have been the issue as my latest build worked and I can verify that everything is properly signed. Dave, thanks very much for your help; you are a great asset to the Eclipse community.
