Re: [cbi-dev] Signing from a container
|That's "just" a good old network routing issue between the cluster and build.eclipse.org Please open a bug so that we can track the resolution of the issue.|
Team Lead - Release Engineering | Eclipse Foundation
📱 (+33) 642 028 039 | 🐦 @mikbarbero
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)
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<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
cbi-dev mailing listcbi-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
Description: Message signed with OpenPGP