Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 549070 - 4.13 build failed with signing issues
Summary: 4.13 build failed with signing issues
Status: CLOSED FIXED
Alias: None
Product: CBI
Classification: Technology
Component: signing-service (show other bugs)
Version: unspecified   Edit
Hardware: All All
: P3 blocker (vote)
Target Milestone: ---   Edit
Assignee: CBI Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 548564
  Show dependency tree
 
Reported: 2019-07-08 10:35 EDT by Sarika Sinha CLA
Modified: 2019-07-17 05:23 EDT (History)
5 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Sarika Sinha CLA 2019-07-08 10:35:56 EDT 
https://download.eclipse.org/eclipse/downloads/drops4/I20190708-0800/buildFailed-run-maven-build

[ERROR] Failed to execute goal org.eclipse.cbi.maven.plugins:eclipse-macsigner-plugin:1.1.5:sign (default) on project org.eclipse.platform.ide: [Mon Jul 08 09:56:02 EDT 2019] Signing of OS X application
Comment 1 Sarika Sinha CLA 2019-07-08 10:42:46 EDT 
I have re triggered the build to see if it was a temporary issue.
Comment 2 Andrey Loskutov CLA 2019-07-08 15:06:08 EDT 
(In reply to Sarika Sinha from comment #1)
> I have re triggered the build to see if it was a temporary issue.

Build is failed again:
http://download.eclipse.org/eclipse/downloads/drops4/I20190708-1035/
Comment 3 Mikaël Barbero CLA 2019-07-08 16:31:53 EDT 
It should be fixed now.
Comment 5 Sarika Sinha CLA 2019-07-11 23:36:10 EDT 
(In reply to Sarika Sinha from comment #4)
> 2 builds failed:
> 
> http://download.eclipse.org/eclipse/downloads/drops4/I20190711-0825/
> http://download.eclipse.org/eclipse/downloads/drops4/I20190711-1120/
> 
> We have a build now:
> http://download.eclipse.org/eclipse/downloads/drops4/I20190711-1805/

This time it was Windows signing-
[ERROR] Failed to execute goal org.eclipse.cbi.maven.plugins:eclipse-winsigner-plugin:1.1.5:sign (default) on project org.eclipse.sdk.ide:  Signing of Windows executable
Comment 6 Mikaël Barbero CLA 2019-07-12 09:48:42 EDT 
for the record, the error is 

[INFO] --- eclipse-winsigner-plugin:1.1.5:sign (default) @ org.eclipse.sdk.ide ---
[INFO] [Thu Jul 11 10:20:58 EDT 2019] Signing Windows executable '/opt/public/eclipse/builds/4I/gitCache/eclipse.platform.releng.aggregator/eclipse.platform.releng.tychoeclipsebuilder/sdk/target/products/org.eclipse.sdk.ide/win32/win32/x86_64/eclipse/eclipsec.exe'
[WARNING] [Thu Jul 11 10:20:58 EDT 2019] HTTP request failed.
HTTP Error 500 (reason: Codesign tool(running on: build,459) exit status: 255.)
CURL failure: Couldn't resolve host name
authenticode timestamping failed

Failed


Error 500: Codesign tool(running on: build,459) exit status: 255.
Server response has been saved to '/opt/public/eclipse/builds/4I/gitCache/eclipse.platform.releng.aggregator/eclipse.platform.releng.tychoeclipsebuilder/sdk/target/products/org.eclipse.sdk.ide/win32/win32/x86_64/eclipse/eclipsec.exe-6674970701661121044-WindowsExeSigner.log'

I'm looking into it, but so far the service has been up and running: https://ci.eclipse.org/cbi/view/sanity-check/job/sanity-check-sign-vm1-windows-signing-service/
Comment 7 Mikaël Barbero CLA 2019-07-12 09:51:02 EDT 
The "CURL failure: Couldn't resolve host name" looks very weird to me. Could you please point me to the pom where the eclipse-winsigner-plugin is invoked? Thanks.
Comment 8 Sarika Sinha CLA 2019-07-12 11:09:33 EDT 
(In reply to Mikaël Barbero from comment #7)
> The "CURL failure: Couldn't resolve host name" looks very weird to me. Could
> you please point me to the pom where the eclipse-winsigner-plugin is
> invoked? Thanks.

/eclipse.platform.releng.aggregator/eclipse.platform.releng.tychoeclipsebuilder/sdk/pom.xml
Comment 10 Mikaël Barbero CLA 2019-07-15 08:36:21 EDT 
I've switched from 

http://timestamp.verisign.com/scripts/timestamp.dll to http://timestamp.comodoca.com as the default timestamping server. Verisign has been pretty unreliable the last couple of days/weeks.
Comment 11 Mikaël Barbero CLA 2019-07-17 03:52:23 EDT 
Do you still face troubles with the windows signer service?
Comment 12 Sarika Sinha CLA 2019-07-17 05:18:13 EDT 
(In reply to Mikaël Barbero from comment #11)
> Do you still face troubles with the windows signer service?

No, we have not faced it after that.
Comment 13 Mikaël Barbero CLA 2019-07-17 05:23:45 EDT 
Thanks for the feedbacks. Closing.