[jbosstools-issues] [JBoss JIRA] (JBIDE-20663) getAndInstallEclipse.groovy :: composite install, Install grinder and p2 director installer jobs need to be updated to support new mars.N filename conventions

[ https://issues.jboss.org/browse/JBIDE-20663?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-20663: ------------------------------------ Yes, we need this, because the old install-grinder can't download this Mars.1 SR3 using the various old properties, since it can't handle a folder that's different (SR1-RC3) from the filename (1-RC3): http://download.eclipse.org/technology/epp/downloads/release/mars/SR1-RC3... To compile this locally, use: {code} cd ~/tru/jbosstools-install-grinder/ mvn clean install ... [INFO] Reactor Summary: [INFO] [INFO] Installation Tests ................................. SUCCESS [ 0.852 s] [INFO] org.jboss.tools.tests.installation ................. SUCCESS [ 10.632 s] [INFO] repository ......................................... SUCCESS [ 4.663 s] [INFO] scripts ............................................ SUCCESS [ 2.992 s] [INFO] BUILD SUCCESS {code} Not sure why you can't find the CR1-SNAPSHOT parent pom. Perhaps it's because of this typo? {code}cd jbosstools-install-gitnder{code} The failures are not because of the new support for the new filename convention at Eclipse. Looking at the master job, http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt... I see {code} 15:05:00 !MESSAGE Internal browser is not available: No more handles [Unknown Mozilla path (MOZILLA_FIVE_HOME not set)] 15:06:23 !MESSAGE Missing requirement: Docker Core Plugin 1.1.0.201509082008 (org.eclipse.linuxtools.docker.core 1.1.0.201509082008) requires 'bundle com.spotify.docker.client 3.1.1' but it could not be found {code} Yet if you check http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-dis... or http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-dis... you'll see *com.spotify.docker.client 3.1.1* at least once in the composite site. And doing the SAME build on the SAME slave, we get a a blue ball 1 time in 3. So... maybe the slave [1] has network issues? [1] http://jenkins.mw.lab.eng.bos.redhat.com/hudson/computer/dev85-rhel6-x86_64 -- This message was sent by Atlassian JIRA (v6.4.11#64026)