Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 530080

Summary:	Build job no longer has access to GPG keys for signing
Product:	Community	Reporter:	Torkild Resheim <torkildr>
Component:	CI-Jenkins	Assignee:	CI Admin Inbox <ci.admin-inbox>
Status:	RESOLVED FIXED	QA Contact:
Severity:	blocker
Priority:	P3	CC:	mikael.barbero, webmaster
Version:	unspecified
Target Milestone:	---
Hardware:	PC
OS:	Mac OS X
Whiteboard:

Description Torkild Resheim

2018-01-20 15:45:43 EST

The Mylyn Docs EPUB release build[1] fails as it is no longer able to access the GPG keys required for signing.

[INFO] [INFO] --- maven-gpg-plugin:1.6:sign (sign-artifacts) @ epub.core ---

[INFO] gpg: problem with the agent: End of file
[INFO] gpg: no default secret key: Operation cancelled
[INFO] gpg: signing failed: Operation cancelled

[1] https://ci.eclipse.org/mylyn/view/Mylyn%20Docs/job/mylyn-docs-epub-release/

Comment 1 Mikaël Barbero

2018-01-22 09:22:02 EST

Thanks for your patience.

Since January 8th, apache-maven-latest symlink has been changed to point from Maven version 3.3.9 to version 3.5.2 (as announced on cross-project on Dec 14th https://dev.eclipse.org/mhonarc/lists/cross-project-issues-dev/msg15076.html). It introduces a regression which prevents Hudson to inject custom settings file (with GPG passphrase) into it. 

As a workaround, I've created a specific tool configuration for Apache Maven version 3.3.9 (named apache-maven-3.3.9) on your HIPP. I've also changed your job "mylyn-docs-epub-release" use it instead of apache-maven-latest. It should fix your issue. If you have other jobs with the same error, just do the same change.

Let us know how it works. Thanks.

Comment 2 Mikaël Barbero

2018-02-21 09:17:15 EST

Marking as resolved. Feel free to reopen if needed.