[
http://jira.jboss.com/jira/browse/JBIDE-1215?page=comments#action_12386038 ]
Marshall Culpepper commented on JBIDE-1215:
-------------------------------------------
Cleaning up the workspace makes sense to me, but cleaning up requirements should be done
by a live person, mainly because of the time it saves. If we forcefully delete all
requirements for every build, we are talking about easily adding another 1-2GB of
downloads to EVERY build, and that will just make it impossible to complete in any sane
amount of time IMO. The problem that you describe above (having multiple old dependencies)
should probably just be more closely monitored when we do a driver upgrade. As part of my
upgrade process, I'll have QA/Prabhat delete the old dependencies before committing.
requirements and workspaces are not cleaned up between tests
------------------------------------------------------------
Key: JBIDE-1215
URL:
http://jira.jboss.com/jira/browse/JBIDE-1215
Project: JBoss Tools
Issue Type: Task
Components: Build/Releng
Reporter: Max Andersen
Assigned To: Marshall Culpepper
Priority: Critical
Fix For: 2.0.0.CR1
Here are the problems we saw in the builds:
1. Requirements should be cleaned up. Now build copies all current and previous
requirements to the eclipse used for JUnit testing. Here is the console output
unzipEclipse:
[echo]
eclipseInstallDir=/home/hudson/jbosstools-build/200710290346-nightly/tests/eclipse-SDK-linux-gtk.tar.gz
[untar] Expanding: /home/hudson/jbosstools-build/eclipse-SDK-linux-gtk.tar.gz into
/home/hudson/jbosstools-build/200710290346-nightly/tests
[echo] Extracting drivers into
/home/hudson/jbosstools-build/200710290346-nightly/tests
[unzip] Expanding: /home/hudson/jbosstools-build/requirements/dtp/dtp-sdk_1.5.1.zip
into /home/hudson/jbosstools-build/200710290346-nightly/tests
[unzip] Expanding: /home/hudson/jbosstools-build/requirements/dtp/dtp-sdk_1.5.zip into
/home/hudson/jbosstools-build/200710290346-nightly/tests
[unzip] Expanding: /home/hudson/jbosstools-build/requirements/dtp/dtp-sdk_1.5RC2.zip
into /home/hudson/jbosstools-build/200710290346-nightly/tests
2. I look through error log and it looks like test are ran on dirty workspace that
contains projects from previous start. Here is an error from log
[java] !ENTRY org.jboss.tools.common.model 4 0 2007-10-29 04:30:07.559
[java] !MESSAGE Resource '/JSFKickStart1/JavaSource' already exists.
[java] !STACK 1
[java] org.eclipse.core.internal.resources.ResourceException: Resource
'/JSFKickStart1/JavaSource' already exists.
[java] at
org.eclipse.core.internal.resources.Resource.checkDoesNotExist(Resource.java:289)
[java] at
org.eclipse.core.internal.resources.Resource.checkDoesNotExist(Resource.java:276)
3. test reports from public site and from QA is different:
QA -
http://reports.qa.atl.jboss.com/binaries/RHDS/nightly/200710270005-nightl...
public -
http://download.jboss.org/jbosstools/builds/nightly/200710251552-nightly/...
Can't at least 2 and 3 be synced up and #1 fixed by unzipping specific requirements
instead of unzipping * ?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira