[
https://issues.jboss.org/browse/JBIDE-12905?page=com.atlassian.jira.plugi...
]
Max Rydahl Andersen commented on JBIDE-12905:
---------------------------------------------
I would like to be able to run and build these installation tests as part of JBT and JBDS
dev-testing, not under QE release cycle(s) for jbosstools-integration-tests which is
*later* than ours.
I dont think this fits in jbosstools-integration-tests which currently is dragging in
mixed bag of reddeer dependencies outside our target platform. As long as that is
happening and they are not build to run within Jenkins standalone nor part of JBT/JBDS
main testing,
we should not mix these up IMO.
so the number of files in here aren't that great (basically just two groovy files)
*BUT* these scripts looks *Extremely* coupled to specific repositories:
"-repository
http://download.eclipse.org/technology/swtbot/helios/dev-build/update-sit... +
"http://download.jboss.org/jbosstools/builds/staging/jbosstools-4.0_trunk.component--base/all/repo/
" +
I grok the swtbot depenendency but why is this dependent on
jbosstools-4.0_trunk.component--base/all/repo ? shouldn't this be run based on what
branch/master we are on ?
I guess because of org.jboss.tools.tests.installation IU, so shouldn't this code
actually *move*/live next with these install scripts ?
About moving out of git, once we figure out where to move them we can run some
filter-branch on it to move with history if necessary.
move base/tests/installation-scripts out
----------------------------------------
Key: JBIDE-12905
URL:
https://issues.jboss.org/browse/JBIDE-12905
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng
Reporter: Max Rydahl Andersen
Assignee: Mickael Istria
Labels: ece2012
Fix For: 4.0.0.CR1
base/tests/scripts/* contains references to upper components in the stack thus its not
really appropriate to have this in the stack.
Options are to move it to its own repo or move to integration-tests - or possibly a
combination.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira