Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[cbi-dev] Signing from a container

Hi all,

There is one last issue in migration of Wild Web Developer to container-ed builds before I think we can say it's done and complete.
It's about signing, it basically doesn't work:
[INFO] --- eclipse-jarsigner-plugin:1.1.5:sign (sign) @ org.eclipse.wildwebdeveloper.tests ---
[INFO] Signing jar: /home/jenkins/workspace/Wildwebdeveloper_master-ROJ4BPCU4Q5VTI7VBBSR4KWQVLVOSBZHJPOZ6FPJL3JEULICJSWQ/org.eclipse.wildwebdeveloper.tests/target/org.eclipse.wildwebdeveloper.tests-0.1.0-SNAPSHOT.jar
[WARNING] [Thu Dec 20 14:10:11 UTC 2018] HTTP request failed.
HTTP Error 403 (reason: Forbidden)
<title>403 Forbidden</title>
<p>You don't have permission to access /sign
on this server.</p>
Server response has been saved to '/home/jenkins/workspace/Wildwebdeveloper_master-ROJ4BPCU4Q5VTI7VBBSR4KWQVLVOSBZHJPOZ6FPJL3JEULICJSWQ/org.eclipse.wildwebdeveloper.tests/target/org.eclipse.wildwebdeveloper.tests-0.1.0-SNAPSHOT.jar-361278314796634130-RemoteJarSigner.log'
As signing happens as part of the Maven build, it needs to be in the project-managed container, it cannot run it on jnlp because many things are missing there.
I guess it could be only a matter of mounting the right volume in the Kubernetes cluster that's described as agent in the Jenkinsfile. Could someone please provide some possible configuration for that?

Thanks in advance
Mickael Istria
Eclipse IDE developer, for Red Hat Developers

Back to the top