[JIRA] Created: (HUDSON-8336) When using CCM with a parameterized build, report generation fails because the parameters are passed to ccm.exe and treated as source folders

classic Classic list List threaded Threaded
8 messages Options
Reply | Threaded
Open this post in threaded view
|

[JIRA] Created: (HUDSON-8336) When using CCM with a parameterized build, report generation fails because the parameters are passed to ccm.exe and treated as source folders

Kohsuke Kawaguchi
Administrator
When using CCM with a parameterized build, report generation fails because the parameters are passed to ccm.exe and treated as source folders
---------------------------------------------------------------------------------------------------------------------------------------------

                 Key: HUDSON-8336
                 URL: http://issues.hudson-ci.org/browse/HUDSON-8336
             Project: Hudson
          Issue Type: Bug
          Components: ccm
    Affects Versions: current
         Environment: Windows 2008 SR2 / Apache Tomcat / Hudson 1.387 / CCM Plugin 1.1
            Reporter: Iristyle
            Assignee: kinow
            Priority: Critical


When a build is parameterized, those parameters are passed to ccm.exe on the command line, and this totally screws up the creation of the ccm.result.xml file.

I have a parameter that accepts a Mercurial revision id.


Here is the relevant section of the build log:

13:00:11  Path To CCM.exe: C:\Program Files (x86)\ccm\bin\ccm.exe
13:00:11  Creating CCM config file C:\Hudson\jobs\Messaging\workspace\ccm.config.xml
13:00:11  Writing CCM configuration into file
13:00:11  <ccm>
13:00:11  <exclude>
13:00:11  <file>*.designer.cs</file>
13:00:11  <folder>contrib</folder>
13:00:11  </exclude>
13:00:11  <analyze>
13:00:11  </analyze>
13:00:11  <recursive>yes</recursive>
13:00:11  <outputXML>yes</outputXML>
13:00:11  <numMetrics>50</numMetrics>
13:00:11  </ccm>
13:00:11  
13:00:11  Executing CCM command: cmd.exe /C " "C:\Program Files (x86)\ccm\bin\ccm.exe" -P:HgRevId=82b039219c2ce8fe029a2384efebcfb6089306fd C:\Hudson\jobs\Messaging\workspace\ccm.config.xml > C:\Hudson\jobs\Messaging\workspace\ccm.result.xml && exit %%ERRORLEVEL%% "
13:00:11  [workspace] $ cmd.exe /C " "C:\Program Files (x86)\ccm\bin\ccm.exe" -P:HgRevId=82b039219c2ce8fe029a2384efebcfb6089306fd C:\Hudson\jobs\Messaging\workspace\ccm.config.xml > C:\Hudson\jobs\Messaging\workspace\ccm.result.xml && exit %%ERRORLEVEL%% "


You'll notice that -P:HgRevId=...

The resultant ccm.result.xml file has this at the top:
-Analyzing folder -P:HgRevId=82b039219c2ce8fe029a2384efebcfb6089306fd.


So please prevent Hudson build parameters from being passed to ccm.exe to solve the issue.

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.hudson-ci.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       
Reply | Threaded
Open this post in threaded view
|

[JIRA] Work started: (HUDSON-8336) When using CCM with a parameterized build, report generation fails because the parameters are passed to ccm.exe and treated as source folders

Kohsuke Kawaguchi
Administrator

     [ http://issues.hudson-ci.org/browse/HUDSON-8336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Work on HUDSON-8336 started by kinow.

> When using CCM with a parameterized build, report generation fails because the parameters are passed to ccm.exe and treated as source folders
> ---------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: HUDSON-8336
>                 URL: http://issues.hudson-ci.org/browse/HUDSON-8336
>             Project: Hudson
>          Issue Type: Bug
>          Components: ccm
>    Affects Versions: current
>         Environment: Windows 2008 SR2 / Apache Tomcat / Hudson 1.387 / CCM Plugin 1.1
>            Reporter: Iristyle
>            Assignee: kinow
>            Priority: Critical
>
> When a build is parameterized, those parameters are passed to ccm.exe on the command line, and this totally screws up the creation of the ccm.result.xml file.
> I have a parameter that accepts a Mercurial revision id.
> Here is the relevant section of the build log:
> 13:00:11  Path To CCM.exe: C:\Program Files (x86)\ccm\bin\ccm.exe
> 13:00:11  Creating CCM config file C:\Hudson\jobs\Messaging\workspace\ccm.config.xml
> 13:00:11  Writing CCM configuration into file
> 13:00:11  <ccm>
> 13:00:11  <exclude>
> 13:00:11  <file>*.designer.cs</file>
> 13:00:11  <folder>contrib</folder>
> 13:00:11  </exclude>
> 13:00:11  <analyze>
> 13:00:11  </analyze>
> 13:00:11  <recursive>yes</recursive>
> 13:00:11  <outputXML>yes</outputXML>
> 13:00:11  <numMetrics>50</numMetrics>
> 13:00:11  </ccm>
> 13:00:11  
> 13:00:11  Executing CCM command: cmd.exe /C " "C:\Program Files (x86)\ccm\bin\ccm.exe" -P:HgRevId=82b039219c2ce8fe029a2384efebcfb6089306fd C:\Hudson\jobs\Messaging\workspace\ccm.config.xml > C:\Hudson\jobs\Messaging\workspace\ccm.result.xml && exit %%ERRORLEVEL%% "
> 13:00:11  [workspace] $ cmd.exe /C " "C:\Program Files (x86)\ccm\bin\ccm.exe" -P:HgRevId=82b039219c2ce8fe029a2384efebcfb6089306fd C:\Hudson\jobs\Messaging\workspace\ccm.config.xml > C:\Hudson\jobs\Messaging\workspace\ccm.result.xml && exit %%ERRORLEVEL%% "
> You'll notice that -P:HgRevId=...
> The resultant ccm.result.xml file has this at the top:
> -Analyzing folder -P:HgRevId=82b039219c2ce8fe029a2384efebcfb6089306fd.
> So please prevent Hudson build parameters from being passed to ccm.exe to solve the issue.

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.hudson-ci.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       
Reply | Threaded
Open this post in threaded view
|

[JIRA] Commented: (HUDSON-8336) When using CCM with a parameterized build, report generation fails because the parameters are passed to ccm.exe and treated as source folders

Kohsuke Kawaguchi
Administrator
In reply to this post by Kohsuke Kawaguchi

    [ http://issues.hudson-ci.org/browse/HUDSON-8336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=144445#action_144445 ]

kinow commented on HUDSON-8336:
-------------------------------

Hi Iristyle, we're working on issue HUDSON-8165. As soon as we have fixed that issue we'll test to see if your issue is still occurring. Get back to you soon :-) Thanks for your report.

> When using CCM with a parameterized build, report generation fails because the parameters are passed to ccm.exe and treated as source folders
> ---------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: HUDSON-8336
>                 URL: http://issues.hudson-ci.org/browse/HUDSON-8336
>             Project: Hudson
>          Issue Type: Bug
>          Components: ccm
>    Affects Versions: current
>         Environment: Windows 2008 SR2 / Apache Tomcat / Hudson 1.387 / CCM Plugin 1.1
>            Reporter: Iristyle
>            Assignee: kinow
>            Priority: Critical
>
> When a build is parameterized, those parameters are passed to ccm.exe on the command line, and this totally screws up the creation of the ccm.result.xml file.
> I have a parameter that accepts a Mercurial revision id.
> Here is the relevant section of the build log:
> 13:00:11  Path To CCM.exe: C:\Program Files (x86)\ccm\bin\ccm.exe
> 13:00:11  Creating CCM config file C:\Hudson\jobs\Messaging\workspace\ccm.config.xml
> 13:00:11  Writing CCM configuration into file
> 13:00:11  <ccm>
> 13:00:11  <exclude>
> 13:00:11  <file>*.designer.cs</file>
> 13:00:11  <folder>contrib</folder>
> 13:00:11  </exclude>
> 13:00:11  <analyze>
> 13:00:11  </analyze>
> 13:00:11  <recursive>yes</recursive>
> 13:00:11  <outputXML>yes</outputXML>
> 13:00:11  <numMetrics>50</numMetrics>
> 13:00:11  </ccm>
> 13:00:11  
> 13:00:11  Executing CCM command: cmd.exe /C " "C:\Program Files (x86)\ccm\bin\ccm.exe" -P:HgRevId=82b039219c2ce8fe029a2384efebcfb6089306fd C:\Hudson\jobs\Messaging\workspace\ccm.config.xml > C:\Hudson\jobs\Messaging\workspace\ccm.result.xml && exit %%ERRORLEVEL%% "
> 13:00:11  [workspace] $ cmd.exe /C " "C:\Program Files (x86)\ccm\bin\ccm.exe" -P:HgRevId=82b039219c2ce8fe029a2384efebcfb6089306fd C:\Hudson\jobs\Messaging\workspace\ccm.config.xml > C:\Hudson\jobs\Messaging\workspace\ccm.result.xml && exit %%ERRORLEVEL%% "
> You'll notice that -P:HgRevId=...
> The resultant ccm.result.xml file has this at the top:
> -Analyzing folder -P:HgRevId=82b039219c2ce8fe029a2384efebcfb6089306fd.
> So please prevent Hudson build parameters from being passed to ccm.exe to solve the issue.

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.hudson-ci.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       
Reply | Threaded
Open this post in threaded view
|

[JIRA] Resolved: (HUDSON-8336) When using CCM with a parameterized build, report generation fails because the parameters are passed to ccm.exe and treated as source folders

Kohsuke Kawaguchi
Administrator
In reply to this post by Kohsuke Kawaguchi

     [ http://issues.hudson-ci.org/browse/HUDSON-8336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

cesar1983 resolved HUDSON-8336.
-------------------------------

         Assignee: cesar1983  (was: kinow)
    Fix Version/s: current
       Resolution: Fixed

The bug was fixed.

There was a wrong parameter inclusion in the ArgumentListBuilder.
It was removed.

> When using CCM with a parameterized build, report generation fails because the parameters are passed to ccm.exe and treated as source folders
> ---------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: HUDSON-8336
>                 URL: http://issues.hudson-ci.org/browse/HUDSON-8336
>             Project: Hudson
>          Issue Type: Bug
>          Components: ccm
>    Affects Versions: current
>         Environment: Windows 2008 SR2 / Apache Tomcat / Hudson 1.387 / CCM Plugin 1.1
>            Reporter: Iristyle
>            Assignee: cesar1983
>            Priority: Critical
>             Fix For: current
>
>
> When a build is parameterized, those parameters are passed to ccm.exe on the command line, and this totally screws up the creation of the ccm.result.xml file.
> I have a parameter that accepts a Mercurial revision id.
> Here is the relevant section of the build log:
> 13:00:11  Path To CCM.exe: C:\Program Files (x86)\ccm\bin\ccm.exe
> 13:00:11  Creating CCM config file C:\Hudson\jobs\Messaging\workspace\ccm.config.xml
> 13:00:11  Writing CCM configuration into file
> 13:00:11  <ccm>
> 13:00:11  <exclude>
> 13:00:11  <file>*.designer.cs</file>
> 13:00:11  <folder>contrib</folder>
> 13:00:11  </exclude>
> 13:00:11  <analyze>
> 13:00:11  </analyze>
> 13:00:11  <recursive>yes</recursive>
> 13:00:11  <outputXML>yes</outputXML>
> 13:00:11  <numMetrics>50</numMetrics>
> 13:00:11  </ccm>
> 13:00:11  
> 13:00:11  Executing CCM command: cmd.exe /C " "C:\Program Files (x86)\ccm\bin\ccm.exe" -P:HgRevId=82b039219c2ce8fe029a2384efebcfb6089306fd C:\Hudson\jobs\Messaging\workspace\ccm.config.xml > C:\Hudson\jobs\Messaging\workspace\ccm.result.xml && exit %%ERRORLEVEL%% "
> 13:00:11  [workspace] $ cmd.exe /C " "C:\Program Files (x86)\ccm\bin\ccm.exe" -P:HgRevId=82b039219c2ce8fe029a2384efebcfb6089306fd C:\Hudson\jobs\Messaging\workspace\ccm.config.xml > C:\Hudson\jobs\Messaging\workspace\ccm.result.xml && exit %%ERRORLEVEL%% "
> You'll notice that -P:HgRevId=...
> The resultant ccm.result.xml file has this at the top:
> -Analyzing folder -P:HgRevId=82b039219c2ce8fe029a2384efebcfb6089306fd.
> So please prevent Hudson build parameters from being passed to ccm.exe to solve the issue.

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.hudson-ci.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       
Reply | Threaded
Open this post in threaded view
|

[JIRA] Reopened: (HUDSON-8336) When using CCM with a parameterized build, report generation fails because the parameters are passed to ccm.exe and treated as source folders

Kohsuke Kawaguchi
Administrator
In reply to this post by Kohsuke Kawaguchi

     [ http://issues.hudson-ci.org/browse/HUDSON-8336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

kinow reopened HUDSON-8336:
---------------------------


We are releasing the new version of the plug-in. We'll close this issue as soon as we have released it.

> When using CCM with a parameterized build, report generation fails because the parameters are passed to ccm.exe and treated as source folders
> ---------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: HUDSON-8336
>                 URL: http://issues.hudson-ci.org/browse/HUDSON-8336
>             Project: Hudson
>          Issue Type: Bug
>          Components: ccm
>    Affects Versions: current
>         Environment: Windows 2008 SR2 / Apache Tomcat / Hudson 1.387 / CCM Plugin 1.1
>            Reporter: Iristyle
>            Assignee: cesar1983
>            Priority: Critical
>
> When a build is parameterized, those parameters are passed to ccm.exe on the command line, and this totally screws up the creation of the ccm.result.xml file.
> I have a parameter that accepts a Mercurial revision id.
> Here is the relevant section of the build log:
> 13:00:11  Path To CCM.exe: C:\Program Files (x86)\ccm\bin\ccm.exe
> 13:00:11  Creating CCM config file C:\Hudson\jobs\Messaging\workspace\ccm.config.xml
> 13:00:11  Writing CCM configuration into file
> 13:00:11  <ccm>
> 13:00:11  <exclude>
> 13:00:11  <file>*.designer.cs</file>
> 13:00:11  <folder>contrib</folder>
> 13:00:11  </exclude>
> 13:00:11  <analyze>
> 13:00:11  </analyze>
> 13:00:11  <recursive>yes</recursive>
> 13:00:11  <outputXML>yes</outputXML>
> 13:00:11  <numMetrics>50</numMetrics>
> 13:00:11  </ccm>
> 13:00:11  
> 13:00:11  Executing CCM command: cmd.exe /C " "C:\Program Files (x86)\ccm\bin\ccm.exe" -P:HgRevId=82b039219c2ce8fe029a2384efebcfb6089306fd C:\Hudson\jobs\Messaging\workspace\ccm.config.xml > C:\Hudson\jobs\Messaging\workspace\ccm.result.xml && exit %%ERRORLEVEL%% "
> 13:00:11  [workspace] $ cmd.exe /C " "C:\Program Files (x86)\ccm\bin\ccm.exe" -P:HgRevId=82b039219c2ce8fe029a2384efebcfb6089306fd C:\Hudson\jobs\Messaging\workspace\ccm.config.xml > C:\Hudson\jobs\Messaging\workspace\ccm.result.xml && exit %%ERRORLEVEL%% "
> You'll notice that -P:HgRevId=...
> The resultant ccm.result.xml file has this at the top:
> -Analyzing folder -P:HgRevId=82b039219c2ce8fe029a2384efebcfb6089306fd.
> So please prevent Hudson build parameters from being passed to ccm.exe to solve the issue.

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.hudson-ci.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       
Reply | Threaded
Open this post in threaded view
|

[JIRA] Updated: (HUDSON-8336) When using CCM with a parameterized build, report generation fails because the parameters are passed to ccm.exe and treated as source folders

Kohsuke Kawaguchi
Administrator
In reply to this post by Kohsuke Kawaguchi

     [ http://issues.hudson-ci.org/browse/HUDSON-8336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

kinow updated HUDSON-8336:
--------------------------

    Fix Version/s:     (was: current)

> When using CCM with a parameterized build, report generation fails because the parameters are passed to ccm.exe and treated as source folders
> ---------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: HUDSON-8336
>                 URL: http://issues.hudson-ci.org/browse/HUDSON-8336
>             Project: Hudson
>          Issue Type: Bug
>          Components: ccm
>    Affects Versions: current
>         Environment: Windows 2008 SR2 / Apache Tomcat / Hudson 1.387 / CCM Plugin 1.1
>            Reporter: Iristyle
>            Assignee: cesar1983
>            Priority: Critical
>
> When a build is parameterized, those parameters are passed to ccm.exe on the command line, and this totally screws up the creation of the ccm.result.xml file.
> I have a parameter that accepts a Mercurial revision id.
> Here is the relevant section of the build log:
> 13:00:11  Path To CCM.exe: C:\Program Files (x86)\ccm\bin\ccm.exe
> 13:00:11  Creating CCM config file C:\Hudson\jobs\Messaging\workspace\ccm.config.xml
> 13:00:11  Writing CCM configuration into file
> 13:00:11  <ccm>
> 13:00:11  <exclude>
> 13:00:11  <file>*.designer.cs</file>
> 13:00:11  <folder>contrib</folder>
> 13:00:11  </exclude>
> 13:00:11  <analyze>
> 13:00:11  </analyze>
> 13:00:11  <recursive>yes</recursive>
> 13:00:11  <outputXML>yes</outputXML>
> 13:00:11  <numMetrics>50</numMetrics>
> 13:00:11  </ccm>
> 13:00:11  
> 13:00:11  Executing CCM command: cmd.exe /C " "C:\Program Files (x86)\ccm\bin\ccm.exe" -P:HgRevId=82b039219c2ce8fe029a2384efebcfb6089306fd C:\Hudson\jobs\Messaging\workspace\ccm.config.xml > C:\Hudson\jobs\Messaging\workspace\ccm.result.xml && exit %%ERRORLEVEL%% "
> 13:00:11  [workspace] $ cmd.exe /C " "C:\Program Files (x86)\ccm\bin\ccm.exe" -P:HgRevId=82b039219c2ce8fe029a2384efebcfb6089306fd C:\Hudson\jobs\Messaging\workspace\ccm.config.xml > C:\Hudson\jobs\Messaging\workspace\ccm.result.xml && exit %%ERRORLEVEL%% "
> You'll notice that -P:HgRevId=...
> The resultant ccm.result.xml file has this at the top:
> -Analyzing folder -P:HgRevId=82b039219c2ce8fe029a2384efebcfb6089306fd.
> So please prevent Hudson build parameters from being passed to ccm.exe to solve the issue.

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.hudson-ci.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       
Reply | Threaded
Open this post in threaded view
|

[JIRA] Resolved: (HUDSON-8336) When using CCM with a parameterized build, report generation fails because the parameters are passed to ccm.exe and treated as source folders

Kohsuke Kawaguchi
Administrator
In reply to this post by Kohsuke Kawaguchi

     [ http://issues.hudson-ci.org/browse/HUDSON-8336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

kinow resolved HUDSON-8336.
---------------------------

    Fix Version/s: current
       Resolution: Fixed

Hi, this issue is fixed in version 2.5. Please, take a look in this version. Thank you for reporting it. Cheers.

> When using CCM with a parameterized build, report generation fails because the parameters are passed to ccm.exe and treated as source folders
> ---------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: HUDSON-8336
>                 URL: http://issues.hudson-ci.org/browse/HUDSON-8336
>             Project: Hudson
>          Issue Type: Bug
>          Components: ccm
>    Affects Versions: current
>         Environment: Windows 2008 SR2 / Apache Tomcat / Hudson 1.387 / CCM Plugin 1.1
>            Reporter: Iristyle
>            Assignee: cesar1983
>            Priority: Critical
>             Fix For: current
>
>
> When a build is parameterized, those parameters are passed to ccm.exe on the command line, and this totally screws up the creation of the ccm.result.xml file.
> I have a parameter that accepts a Mercurial revision id.
> Here is the relevant section of the build log:
> 13:00:11  Path To CCM.exe: C:\Program Files (x86)\ccm\bin\ccm.exe
> 13:00:11  Creating CCM config file C:\Hudson\jobs\Messaging\workspace\ccm.config.xml
> 13:00:11  Writing CCM configuration into file
> 13:00:11  <ccm>
> 13:00:11  <exclude>
> 13:00:11  <file>*.designer.cs</file>
> 13:00:11  <folder>contrib</folder>
> 13:00:11  </exclude>
> 13:00:11  <analyze>
> 13:00:11  </analyze>
> 13:00:11  <recursive>yes</recursive>
> 13:00:11  <outputXML>yes</outputXML>
> 13:00:11  <numMetrics>50</numMetrics>
> 13:00:11  </ccm>
> 13:00:11  
> 13:00:11  Executing CCM command: cmd.exe /C " "C:\Program Files (x86)\ccm\bin\ccm.exe" -P:HgRevId=82b039219c2ce8fe029a2384efebcfb6089306fd C:\Hudson\jobs\Messaging\workspace\ccm.config.xml > C:\Hudson\jobs\Messaging\workspace\ccm.result.xml && exit %%ERRORLEVEL%% "
> 13:00:11  [workspace] $ cmd.exe /C " "C:\Program Files (x86)\ccm\bin\ccm.exe" -P:HgRevId=82b039219c2ce8fe029a2384efebcfb6089306fd C:\Hudson\jobs\Messaging\workspace\ccm.config.xml > C:\Hudson\jobs\Messaging\workspace\ccm.result.xml && exit %%ERRORLEVEL%% "
> You'll notice that -P:HgRevId=...
> The resultant ccm.result.xml file has this at the top:
> -Analyzing folder -P:HgRevId=82b039219c2ce8fe029a2384efebcfb6089306fd.
> So please prevent Hudson build parameters from being passed to ccm.exe to solve the issue.

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.hudson-ci.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       
Reply | Threaded
Open this post in threaded view
|

[JIRA] Updated: (HUDSON-8336) When using CCM with a parameterized build, report generation fails because the parameters are passed to ccm.exe and treated as source folders

Kohsuke Kawaguchi
Administrator
In reply to this post by Kohsuke Kawaguchi

     [ http://issues.hudson-ci.org/browse/HUDSON-8336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

kinow updated HUDSON-8336:
--------------------------

    Status: Verified  (was: Resolved)

> When using CCM with a parameterized build, report generation fails because the parameters are passed to ccm.exe and treated as source folders
> ---------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: HUDSON-8336
>                 URL: http://issues.hudson-ci.org/browse/HUDSON-8336
>             Project: Hudson
>          Issue Type: Bug
>          Components: ccm
>    Affects Versions: current
>         Environment: Windows 2008 SR2 / Apache Tomcat / Hudson 1.387 / CCM Plugin 1.1
>            Reporter: Iristyle
>            Assignee: cesar1983
>            Priority: Critical
>             Fix For: current
>
>
> When a build is parameterized, those parameters are passed to ccm.exe on the command line, and this totally screws up the creation of the ccm.result.xml file.
> I have a parameter that accepts a Mercurial revision id.
> Here is the relevant section of the build log:
> 13:00:11  Path To CCM.exe: C:\Program Files (x86)\ccm\bin\ccm.exe
> 13:00:11  Creating CCM config file C:\Hudson\jobs\Messaging\workspace\ccm.config.xml
> 13:00:11  Writing CCM configuration into file
> 13:00:11  <ccm>
> 13:00:11  <exclude>
> 13:00:11  <file>*.designer.cs</file>
> 13:00:11  <folder>contrib</folder>
> 13:00:11  </exclude>
> 13:00:11  <analyze>
> 13:00:11  </analyze>
> 13:00:11  <recursive>yes</recursive>
> 13:00:11  <outputXML>yes</outputXML>
> 13:00:11  <numMetrics>50</numMetrics>
> 13:00:11  </ccm>
> 13:00:11  
> 13:00:11  Executing CCM command: cmd.exe /C " "C:\Program Files (x86)\ccm\bin\ccm.exe" -P:HgRevId=82b039219c2ce8fe029a2384efebcfb6089306fd C:\Hudson\jobs\Messaging\workspace\ccm.config.xml > C:\Hudson\jobs\Messaging\workspace\ccm.result.xml && exit %%ERRORLEVEL%% "
> 13:00:11  [workspace] $ cmd.exe /C " "C:\Program Files (x86)\ccm\bin\ccm.exe" -P:HgRevId=82b039219c2ce8fe029a2384efebcfb6089306fd C:\Hudson\jobs\Messaging\workspace\ccm.config.xml > C:\Hudson\jobs\Messaging\workspace\ccm.result.xml && exit %%ERRORLEVEL%% "
> You'll notice that -P:HgRevId=...
> The resultant ccm.result.xml file has this at the top:
> -Analyzing folder -P:HgRevId=82b039219c2ce8fe029a2384efebcfb6089306fd.
> So please prevent Hudson build parameters from being passed to ccm.exe to solve the issue.

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.hudson-ci.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira