java.lang.Exception: No file matches the specified pattern:target/site/clover/**/clover.xml in [/var/bamboo-home/xml-data/build-dir/ANT-JOB1]

Atlassian JIRA | Jeremy Owen [Atlassian] | 10 months ago
tip
Your exception is missing from the Samebug knowledge base.
Here are the best solutions we found on the Internet.
Click on the to mark the helpful solution and get rewards for you help.
  1. 0

    h3. Summary With automatic integration, Clover Results Collector tries to find clover.xml in the wrong subdirectory in a job that involves an Ant task when another non-VCS checkout task (e.g. Script) is present above it in the task order. The search pattern applied is: {{/target/site/clover/**/clover.xml}} (which is applicable for Maven tasks) Instead of: {{/clover/**/clover.xml}} (for Ant) Impact: Clover tab is not visible for a Job. Clover statistics are not available in build Metadata after the build. h3. Steps to Reproduce # Create a basic plan and job # Setup the following task order: ## Script ## Source code checkout ## Ant build # Go to the miscellaneous tab of the job and: ## Check 'Use Clover to collect Code Coverage for this build.' ## Enable 'Automatically integrate Clover into this build.' # Save (Regardless of if you've changed the clover integration setting. This should trigger the clover XML location to update incorrectly based on the first task) # Trigger a build h3. Expected Results Clover Results Collector tries to find clover.xml in the correct pattern for Ant: /clover/**/clover.xml h3. Actual Results The below exception is reported in atlassian-bamboo.log {noformat} [ExecuteBuildTask] Failed to execute plugin with class com.atlassian.bamboo.clover.builder.coverage.CloverBuildProcessor : ANT-JOB1-1 java.lang.Exception: No file matches the specified pattern:target/site/clover/**/clover.xml in [/var/bamboo-home/xml-data/build-dir/ANT-JOB1] at com.atlassian.bamboo.clover.builder.coverage.CloverBuildProcessor.call(CloverBuildProcessor.java:156) at com.atlassian.bamboo.build.pipeline.tasks.ExecuteBuildTask.performCustomBuildProcess(ExecuteBuildTask.java:158) at com.atlassian.bamboo.build.pipeline.tasks.ExecuteBuildTask.call(ExecuteBuildTask.java:79) at com.atlassian.bamboo.v2.build.agent.DefaultBuildAgent.build(DefaultBuildAgent.java:215) at com.atlassian.bamboo.v2.build.agent.BuildAgentControllerImpl$1.call(BuildAgentControllerImpl.java:139) at com.atlassian.bamboo.v2.build.agent.BuildAgentControllerImpl$1.call(BuildAgentControllerImpl.java:130) at com.atlassian.bamboo.variable.CustomVariableContextImpl.withVariableSubstitutor(CustomVariableContextImpl.java:221) at com.atlassian.bamboo.v2.build.agent.BuildAgentControllerImpl.waitAndPerformBuild(BuildAgentControllerImpl.java:129) at com.atlassian.bamboo.v2.build.agent.DefaultBuildAgent$1.run(DefaultBuildAgent.java:137) at com.atlassian.bamboo.utils.BambooRunnables$1.run(BambooRunnables.java:51) at com.atlassian.bamboo.security.ImpersonationHelper.runWith(ImpersonationHelper.java:31) at com.atlassian.bamboo.security.ImpersonationHelper.runWithSystemAuthority(ImpersonationHelper.java:20) at com.atlassian.bamboo.security.ImpersonationHelper$1.run(ImpersonationHelper.java:52) at java.lang.Thread.run(Thread.java:745) {noformat} Following is present in the build log: {noformat} Failed to execute plugin 'Clover Results Collector' with error: No file matches the specified pattern:target/site/clover/**/clover.xml in [/var/bamboo-home/xml-data/build-dir/ANT-JOB1] {noformat} h3.Workaround # Configure the plan and job. # Move the Ant task to the top of the job so it's the first task # Go to the miscellaneous tab of the job: ## Ensure 'Automatically integrate Clover into this build.' is checked. ## Save - regardless of whether changes are made to automatically integrate clover. This should trigger a path update with Ant as the first task. # Go back to the Task tab and return the Ant task to it's appropriate position in the job. (Don't save the miscellaneous tab again after you've moved Ant back down the task order)

    Atlassian JIRA | 10 months ago | Jeremy Owen [Atlassian]
    java.lang.Exception: No file matches the specified pattern:target/site/clover/**/clover.xml in [/var/bamboo-home/xml-data/build-dir/ANT-JOB1]
  2. 0

    h3. Summary With automatic integration, Clover Results Collector tries to find clover.xml in the wrong subdirectory in a job that involves an Ant task when another non-VCS checkout task (e.g. Script) is present above it in the task order. The search pattern applied is: {{/target/site/clover/**/clover.xml}} (which is applicable for Maven tasks) Instead of: {{/clover/**/clover.xml}} (for Ant) Impact: Clover tab is not visible for a Job. Clover statistics are not available in build Metadata after the build. h3. Steps to Reproduce # Create a basic plan and job # Setup the following task order: ## Script ## Source code checkout ## Ant build # Go to the miscellaneous tab of the job and: ## Check 'Use Clover to collect Code Coverage for this build.' ## Enable 'Automatically integrate Clover into this build.' # Save (Regardless of if you've changed the clover integration setting. This should trigger the clover XML location to update incorrectly based on the first task) # Trigger a build h3. Expected Results Clover Results Collector tries to find clover.xml in the correct pattern for Ant: /clover/**/clover.xml h3. Actual Results The below exception is reported in atlassian-bamboo.log {noformat} [ExecuteBuildTask] Failed to execute plugin with class com.atlassian.bamboo.clover.builder.coverage.CloverBuildProcessor : ANT-JOB1-1 java.lang.Exception: No file matches the specified pattern:target/site/clover/**/clover.xml in [/var/bamboo-home/xml-data/build-dir/ANT-JOB1] at com.atlassian.bamboo.clover.builder.coverage.CloverBuildProcessor.call(CloverBuildProcessor.java:156) at com.atlassian.bamboo.build.pipeline.tasks.ExecuteBuildTask.performCustomBuildProcess(ExecuteBuildTask.java:158) at com.atlassian.bamboo.build.pipeline.tasks.ExecuteBuildTask.call(ExecuteBuildTask.java:79) at com.atlassian.bamboo.v2.build.agent.DefaultBuildAgent.build(DefaultBuildAgent.java:215) at com.atlassian.bamboo.v2.build.agent.BuildAgentControllerImpl$1.call(BuildAgentControllerImpl.java:139) at com.atlassian.bamboo.v2.build.agent.BuildAgentControllerImpl$1.call(BuildAgentControllerImpl.java:130) at com.atlassian.bamboo.variable.CustomVariableContextImpl.withVariableSubstitutor(CustomVariableContextImpl.java:221) at com.atlassian.bamboo.v2.build.agent.BuildAgentControllerImpl.waitAndPerformBuild(BuildAgentControllerImpl.java:129) at com.atlassian.bamboo.v2.build.agent.DefaultBuildAgent$1.run(DefaultBuildAgent.java:137) at com.atlassian.bamboo.utils.BambooRunnables$1.run(BambooRunnables.java:51) at com.atlassian.bamboo.security.ImpersonationHelper.runWith(ImpersonationHelper.java:31) at com.atlassian.bamboo.security.ImpersonationHelper.runWithSystemAuthority(ImpersonationHelper.java:20) at com.atlassian.bamboo.security.ImpersonationHelper$1.run(ImpersonationHelper.java:52) at java.lang.Thread.run(Thread.java:745) {noformat} Following is present in the build log: {noformat} Failed to execute plugin 'Clover Results Collector' with error: No file matches the specified pattern:target/site/clover/**/clover.xml in [/var/bamboo-home/xml-data/build-dir/ANT-JOB1] {noformat} h3.Workaround # Configure the plan and job. # Move the Ant task to the top of the job so it's the first task # Go to the miscellaneous tab of the job: ## Ensure 'Automatically integrate Clover into this build.' is checked. ## Save - regardless of whether changes are made to automatically integrate clover. This should trigger a path update with Ant as the first task. # Go back to the Task tab and return the Ant task to it's appropriate position in the job. (Don't save the miscellaneous tab again after you've moved Ant back down the task order)

    Atlassian JIRA | 10 months ago | Jeremy Owen [Atlassian]
    java.lang.Exception: No file matches the specified pattern:target/site/clover/**/clover.xml in [/var/bamboo-home/xml-data/build-dir/ANT-JOB1]
  3. 0

    org.jboss.as.logging issue with really simple jaxrs project

    Google Groups | 1 year ago | Sebastien Blanc
    java.lang.Exception: WFLYSRV0056: Server boot has failed in an > unrecoverable manner; exiting. See previous messages for details. > at > org.jboss.as.server.BootstrapListener.bootFailure(BootstrapListener.java:87) > at org.jboss.as.server.ServerService.boot(ServerService.java:384)
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0

    Cannot open Planning application : An error occ... | Oracle Community

    oracle.com | 12 months ago
    java.lang.Exception: No object were successfully created. This can be caused by any of the following: The OLAP Server is not running, The DBMS is not running, the DBMS is running on a different machine that the one specified, the name and password provided were incorrect.
  6. 0

    Java applet failed to run - Java Programming Help - KnowCoding.com

    knowcoding.com | 2 years ago
    java.lang.Exception: Unable to get input stream for lwjgl.jar at org.lwjgl.util.applet.AppletLoader.getJarInputStre am(AppletLoader.java:1607) at org.lwjgl.util.applet.AppletLoader.downloadJars(Ap pletLoader.java:1479) at org.lwjgl.util.applet.AppletLoader.run(AppletLoade r.java:871)

    Not finding the right solution?
    Take a tour to get the most out of Samebug.

    Tired of useless tips?

    Automated exception search integrated into your IDE

    Root Cause Analysis

    1. java.lang.Exception

      No file matches the specified pattern:target/site/clover/**/clover.xml in [/var/bamboo-home/xml-data/build-dir/ANT-JOB1]

      at com.atlassian.bamboo.clover.builder.coverage.CloverBuildProcessor.call()
    2. com.atlassian.bamboo
      ImpersonationHelper$1.run
      1. com.atlassian.bamboo.clover.builder.coverage.CloverBuildProcessor.call(CloverBuildProcessor.java:156)
      2. com.atlassian.bamboo.build.pipeline.tasks.ExecuteBuildTask.performCustomBuildProcess(ExecuteBuildTask.java:158)
      3. com.atlassian.bamboo.build.pipeline.tasks.ExecuteBuildTask.call(ExecuteBuildTask.java:79)
      4. com.atlassian.bamboo.v2.build.agent.DefaultBuildAgent.build(DefaultBuildAgent.java:215)
      5. com.atlassian.bamboo.v2.build.agent.BuildAgentControllerImpl$1.call(BuildAgentControllerImpl.java:139)
      6. com.atlassian.bamboo.v2.build.agent.BuildAgentControllerImpl$1.call(BuildAgentControllerImpl.java:130)
      7. com.atlassian.bamboo.variable.CustomVariableContextImpl.withVariableSubstitutor(CustomVariableContextImpl.java:221)
      8. com.atlassian.bamboo.v2.build.agent.BuildAgentControllerImpl.waitAndPerformBuild(BuildAgentControllerImpl.java:129)
      9. com.atlassian.bamboo.v2.build.agent.DefaultBuildAgent$1.run(DefaultBuildAgent.java:137)
      10. com.atlassian.bamboo.utils.BambooRunnables$1.run(BambooRunnables.java:51)
      11. com.atlassian.bamboo.security.ImpersonationHelper.runWith(ImpersonationHelper.java:31)
      12. com.atlassian.bamboo.security.ImpersonationHelper.runWithSystemAuthority(ImpersonationHelper.java:20)
      13. com.atlassian.bamboo.security.ImpersonationHelper$1.run(ImpersonationHelper.java:52)
      13 frames
    3. Java RT
      Thread.run
      1. java.lang.Thread.run(Thread.java:745)
      1 frame