Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[orbit-dev] RE: Orbit should promote a new build with the new certificate

Hi all,
 
so I was able to build I20090202003856:
http://download.eclipse.org/tools/orbit/committers/
 
but according to CruiseControl there was a compile error:
http://build.eclipse.org:9777/cruisecontrol/buildresults/orbit-I?tab=buildResults
[javac] Compile failed; see the compiler error output for details.
Clicking on the "build artifacts" link produces a 404 not Found.
I did not find out how to access the compiler error output from CruiseControl,
so I'm afraid I'm lost at this point... and not going to promote a build that looks
good but that's probably broken. Any help is appreciated at this point.
Cheers,
--
Martin Oberhuber, Senior Member of Technical Staff, Wind River
Target Management Project Lead, DSDP PMC Member
http://www.eclipse.org/dsdp/tm
 
 


From: Oberhuber, Martin
Sent: Montag, 02. Februar 2009 01:04
To: 'Orbit Developer discussion'
Subject: Orbit should promote a new build with the new certificate

Hi all,
 
a new certificate for signing was installed on the Eclipse.org servers this Friday.
 
There are chances that the latest Orbit S-build being signed with the old certificate interferes badly with Eclipse builds leveraging the new certificate:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=263032#c19
 
I think that we should proactively declare a new build. I just kicked one; according to history of the bundles.map file, no changes have been released since 23-Jan-2009, so we should be good to declare the build stable. I'm not sure if I'll need help for this...
https://bugs.eclipse.org/bugs/show_bug.cgi?id=263032#c23
 
Cheers,
--
Martin Oberhuber, Senior Member of Technical Staff, Wind River
Target Management Project Lead, DSDP PMC Member
http://www.eclipse.org/dsdp/tm
 
 

Back to the top