[ https://issues.jboss.org/browse/JBIDE-12946?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-12946: ------------------------------- Description: Need your help here. I've migrated https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... to use 15 git repos and run a mvn build 7 times (2 x bootstrap builds for central and birt, then 5 x single component builds). But I'm getting this error: {code} [WARNING] The requested profile "coverage" could not be activated because it does not exist. [WARNING] The requested profile "local.requirements" could not be activated because it does not exist. {code} Can you work your magic to enable code coverage for this job? Also, can you enable the "test failures are yellow, not red" stuff you did for the other component jobs? That way we can get results for ALL the mvn runs when hibernate's tests fail, rather than the job crapping out on the first failed test. was: Need your help here. I've migrated https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... to use 15 git repos and run a mvn build 7 times (2 x bootstrap builds for central and birt, then 5 x single component builds). But I'm getting this error: {code} [WARNING] The requested profile "coverage" could not be activated because it does not exist. [WARNING] The requested profile "local.requirements" could not be activated because it does not exist. {code} Can you work your magic to enable code coverage for this job? -- 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

[ https://issues.jboss.org/browse/JBIDE-12946?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-12946: ---------------------------------------- The job has flag -Dswtbot.test.skip=true. Is this really what we want? -- 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

[ https://issues.jboss.org/browse/JBIDE-12946?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-12946 at 11/12/12 10:22 AM: --------------------------------------------------------------- I'm guessing no. If we've successfully figured out how to run all the tests (xvfb, xvnc?) with all the required -Dflags / jvmoptions, including {code} -Djbosstools.test.jre.5="${NATIVE_TOOLS}${SEP}${JAVA15}" -Djbosstools.test.jre.6="${NATIVE_TOOLS}${SEP}${JAVA16}" {code} then we should be running everything: bot and non-ui tests alike. was (Author: nickboldt): I'm guessing no. If we've successfully figured out how to run all the tests (xvfb, xvnc?) with all the required -Dflags / jvmoptions, including {{-Djbosstools.test.jre.5="${NATIVE_TOOLS}${SEP}${JAVA15}" -Djbosstools.test.jre.6="${NATIVE_TOOLS}${SEP}${JAVA16}"}} then we should be running everything: bot and non-ui tests alike. -- 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

[ https://issues.jboss.org/browse/JBIDE-12946?page=com.atlassian.jira.plugi... ] Mickael Istria edited comment on JBIDE-12946 at 11/12/12 12:50 PM: ------------------------------------------------------------------- Real reasons why tests are missing are: * Not all modules actually have a mvn execution * the "-P bootstrap" profile does nothing I think maintaining the list of repo and mvn execution in the job is complicated and ugly, that's why I'd like to suggest usage of a "Facade" repo that would make it easier to configure a "All tests" or "All build" job: https://github.com/mickaelistria/jbosstools-all But it also appears the this all tests job is useless. As a workaround, we can simply fix the list of mvn executions, but that's less cool than using a facade repo. was (Author: mickael_istria): REad reason why tests are missing are: * Not all modules actually have a mvn execution * the "-P bootstrap" profile does nothing I think maintaining the list of repo and mvn execution in the job is complicated and ugly, that's why I'd like to suggest usage of a "Facade" repo that would make it easier to configure a "All tests" or "All build" job: https://github.com/mickaelistria/jbosstools-all But it also appears the this all tests job is useless. As a workaround, we can simply fix the list of mvn executions, but that's less cool than using a facade repo. -- 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

[ https://issues.jboss.org/browse/JBIDE-12946?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-12946: ------------------------------------ https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... now runs 1281 tests. On Jan 28 2012, there were 4070 tests, including 35 failures (-47), 13 skipped (+13). -- 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

[ https://issues.jboss.org/browse/JBIDE-12946?page=com.atlassian.jira.plugi... ] Mickael Istria edited comment on JBIDE-12946 at 11/16/12 2:45 AM: ------------------------------------------------------------------ Postponed. We need to find out whether we want to keep tests. was (Author: mickael_istria): Postponed. We need to agree on a location to host installation-tests. -- 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

[ https://issues.jboss.org/browse/JBIDE-12946?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-12946: --------------------------------------------- assigning to Denis so he sees it. Denis - I forget what reasons we have now to run this job when jenkins can accumulate the results dynamically. Do you recall? -- 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

[ https://issues.jboss.org/browse/JBIDE-12946?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-12946: --------------------------------------------- Talked with Denis - can't recall any good reason for keeping it aorund it is current form. Might be found later but for now - not a big need. -- 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

[ https://issues.jboss.org/browse/JBIDE-12946?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-12946: ------------------------------------ Job disabled and moved here: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... Will be archived in SVN and then eventually garbage collected from Jenkins when/if we decide we no longer need the job. -- 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