Nick Boldt created JBIDE-11599: ---------------------------------- Summary: SOA Tooling .tests & .continuous jobs are misconfigured: profiles not found, no tests run Key: JBIDE-11599 URL: https://issues.jboss.org/browse/JBIDE-11599 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: Build/Releng, SOA Tooling Affects Versions: 3.3.0.Beta3-SOA Reporter: Nick Boldt Assignee: Mickael Istria Fix For: 3.3.0.Beta3-SOA http://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_trunk.soa-tooling.te... [INFO] Reactor Summary: [INFO] [INFO] emma-coverage ..................................... SUCCESS [26.106s] [INFO] org.jboss.tools.build ............................. SUCCESS [0.013s] [INFO] ------------------------------------------------------------------------ [INFO] BUILD SUCCESS [INFO] ------------------------------------------------------------------------ [INFO] Total time: 46.709s [INFO] Finished at: Thu Apr 19 17:39:02 EDT 2012 [INFO] Final Memory: 4M/490M [INFO] ------------------------------------------------------------------------ [WARNING] The requested profile "coverage" could not be activated because it does not exist. [WARNING] The requested profile "local.site" could not be activated because it does not exist. [WARNING] The requested profile "local.composite" could not be activated because it does not exist. [WARNING] The requested profile "local.requirements" could not be activated because it does not exist. [WARNING] The requested profile "jbosstools-nightly-staging-composite" could not be activated because it does not exist. This build should be running all the <activeByDefault>true</activeByDefault> profiles in https://anonsvn.jboss.org/repos/jbosstools/trunk/build/pom-soa-tooling.xml, and producing test results for those components. For the .continuous job, everything should be compiled but tests are not run. https://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_trunk.soa-tooling.t... https://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_trunk.soa-tooling.c... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira