Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 322869 - SDK zip name not match to eclipse-Automated-Tests-3.6.zip
Summary: SDK zip name not match to eclipse-Automated-Tests-3.6.zip
Status: CLOSED DUPLICATE of bug 110852
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Releng (show other bugs)
Version: 4.0   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform-Releng-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-08-17 02:00 EDT by Urs Frei CLA
Modified: 2011-03-15 14:44 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Urs Frei CLA 2010-08-17 02:00:27 EDT
Build Identifier: Eclipse 3.6 (I20100608-0911)

I had some problem with "Automated Testing of Eclipse Build". I downloaded 
the file eclpse-Automated-Tests-3.6.zip and other. After I installed every 
thing, I couldn't run it. The problem was: the eclipse sdk zip had the wrong 
name. I had to rename it from eclipse-SDK-3.6-win32.zip to 
eclipse-SDK-I20100608-0911-win32.zip. I don't know why.
I needed a lot of time to find this solution. For the future I think we 
should change the test.xml to have an idea where the problem is. Could we 
change in the test.xml the line 62 from <exec dir="." executable="unzip"> to 
<exec dir="." executable="unzip" failonerror="true">  (add failonerror)

Andrew Niefer answered
*************************************************************************
The problem comes from the fact that when we are approaching the release,
all the builds are named like eclipse-SDK-I20100608-0911-win32.zip.

Once a particular build is declared to be the final one, then the zips just
get renamed (eclipse-SDK-3.6-win32.zip), but I guess the test scripts still
refer to the original name.
*************************************************************************

Reproducible: Always
Comment 1 DJ Houghton CLA 2010-08-18 15:45:07 EDT
The problems seems to be that the label.properties file which is included in the test zip still contains the old build id and this is the value which is passed into the test.xml file which does the setup. I've changed the values in this file to be "3.6" and the tests ran correctly.

Whether the process is manual or automatic, we should add this file to the list of things to change when we promote a build.
Comment 2 Kim Moir CLA 2011-03-15 14:44:33 EDT

*** This bug has been marked as a duplicate of bug 110852 ***