-
Bug
-
Resolution: Cannot Reproduce
-
Trivial
-
None
-
Windows server 2003
Memory map plugin from Praqma does not allow to enter absolute or relative path.
This is required for our build because the .cmd and .map files are found in directories relative to the Jenkins job workspace.
I have tried both relative and absolute path without success. Here is an example of absolute path usage:
C:\Hudson\jobs\VALHAL_MC_Commit_Workspace_Server1\workspace\MC>exit 0
Checking console output
C:\Hudson\jobs\VALHAL_DSP_Build\builds\2014-07-10_08-50-11\log:
C:\Hudson\jobs\VALHAL_MC_Commit_Workspace_Server1\workspace\MC>echo INFO - HUDSON_JOB_SUCCEED
Memory Map Plugin version 1.0.2
java.io.IOException: Filematcher found no files using pattern C:\Hudson\jobs\VALHAL_DSP_Build\workspace\DSP\mc.cmd in folder C:\Hudson\jobs\VALHAL_DSP_Build\workspace
at net.praqma.jenkins.memorymap.parser.MemoryMapConfigFileParserDelegate.invoke(MemoryMapConfigFileParserDelegate.java:64)
at net.praqma.jenkins.memorymap.parser.MemoryMapConfigFileParserDelegate.invoke(MemoryMapConfigFileParserDelegate.java:42)
at hudson.FilePath.act(FilePath.java:920)
at hudson.FilePath.act(FilePath.java:893)
at net.praqma.jenkins.memorymap.MemoryMapRecorder.perform(MemoryMapRecorder.java:100)
at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:45)
at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:756)
at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:720)
at hudson.model.Build$BuildExecution.post2(Build.java:182)
at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:669)
at hudson.model.Run.execute(Run.java:1735)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:234)
Printing configuration
Build step 'Memory Map Publisher' changed build result to FAILURE
Build step 'Memory Map Publisher' marked build as failure
Warning: you have no plugins providing access control for builds, so falling back to legacy behavior of permitting any downstream builds to be triggered
Finished: FAILURE