Bugzilla – Full Text Bug Listing
| Summary: | Signer down | ||
|---|---|---|---|
| Product: | Community | Reporter: | Ed Willink <ed> |
| Component: | CI-Jenkins | Assignee: | CI Admin Inbox <ci.admin-inbox> |
| Status: | CLOSED FIXED | QA Contact: | |
| Severity: | critical | ||
| Priority: | P3 | CC: | achim.kraus, Ed.Merks, mikael.barbero, webmaster |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows 10 | ||
| Whiteboard: | |||
|
Description
Ed Willink
Fixed. The build.eclipse.org:31338 proxy was down. Note though that the new URL (hosted at https://cbi.eclipse.org as listed here https://wiki.eclipse.org/IT_Infrastructure_Doc#Web_service) was still up and running. See https://www.eclipse.org/lists/cross-project-issues-dev/msg18330.html for details how to use those new urls. (In reply to Mikaël Barbero from comment #1) > See https://www.eclipse.org/lists/cross-project-issues-dev/msg18330.html for > details how to use those new urls. Running Tycho with the versions:display-plugin-updates goal to see what is new does not reveal the new 1.3.0 version of eclipse-jarsigner-plugin. Rather [WARNING] The POM for org.eclipse.cbi.maven.plugins:eclipse-jarsigner-plugin:jar:1.1.2 is missing, no dependency information available [WARNING] Failed to retrieve plugin descriptor for org.eclipse.cbi.maven.plugins:eclipse-jarsigner-plugin:1.1.2: Plugin org.eclipse.cbi.maven.plugins:eclipse-jarsigner-plugin:1.1.2 or one of its dependencies could not be resolved: Failure to find org.eclipse.cbi.maven.plugins:eclipse-jarsigner-plugin:jar:1.1.2 in https://repo.maven.apache.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced cbi maven plugins are not published on maven central, only on repo.eclipse.org. Do your command again, this time with -Dmaven.repo.remote=https://repo.eclipse.org This build is failing: https://ci.eclipse.org/emf/job/integration/597/console [ERROR] Failed to execute goal org.eclipse.cbi.maven.plugins:eclipse-jarsigner-plugin:1.1.7:sign (sign) on project org.eclipse.emf.activities: [Sun Jul 04 09:43:46 EDT 2021] Unable to sign jar '/opt/public/hipp/homes/genie.emf/workspace/integration/git/org.eclipse.emf/examples/org.eclipse.emf.activities/target/org.eclipse.emf.activities-2.7.0-SNAPSHOT.jar': Connect to build.eclipse.org:31338 [build.eclipse.org/198.41.30.203] failed: Connection refused (Connection refused) -> [Help 1] This one too. I've seen no outage this time. When I raised this bug I had not responded to the new Tycho support for the migrated signer. It seems that build.eclipse.org is increasingly fragile, so it seems prudent to follow the advice asap. Just change eclipse-jarsigner-version to 1.3.1 in pom.xml as per https://git.eclipse.org/r/plugins/gitiles/mmt/org.eclipse.qvto/+/e46641ed45e603615787b674331de58f4478495d%5E%21/#F0 While tweaking pom.xml, it is also prudent to phase out pack200, Bug 572316, Just delete all plugins around "pack200" in pom.xml as per https://git.eclipse.org/r/plugins/gitiles/mmt/org.eclipse.qvto/+/refs/heads/master%5E%21/#F0 That was once again the old build.eclipse.org:31338 that went down. Users of cbi.eclipse.org did not see experience any outage. I've restarted build.eclipse.org:31338 and old URLs are back in service. *** Bug 574650 has been marked as a duplicate of this bug. *** |