[
https://issues.jenkins-ci.org/browse/JENKINS-13954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=163344#comment-163344
]
Gregory Boissinot commented on JENKINS-13954:
---------------------------------------------
I understand your use case.
I am not sure if your proposal is the right solution.
Maybe a combination of the Flexible Publisher Plugin
(https://wiki.jenkins-ci.org/display/JENKINS/Flexible+Publish+Plugin) and the
Run Condition plugin
(https://wiki.jenkins-ci.org/display/JENKINS/Run+Condition+Plugin) could
achieve your target.
I have not ever tested but could you try and let me know.
> Add an option so that the build doesn't fail if cppcheck can't find the XML
> file.
> ---------------------------------------------------------------------------------
>
> Key: JENKINS-13954
> URL: https://issues.jenkins-ci.org/browse/JENKINS-13954
> Project: Jenkins
> Issue Type: Improvement
> Components: cppcheck
> Affects Versions: current
> Reporter: Verbitan
> Assignee: Gregory Boissinot
> Priority: Minor
>
> I've got a multi-configuration job which compiles on both Linux and Solaris.
> The cppcheck binary I use is compiled for Solaris and not Linux, so in the
> job configuration I only generate the cppcheck XML if the build is being run
> on Solaris.
> I want to publish out the cppcheck results, but this always causes the Linux
> build to fail as it hasn't generated the XML file.
> Is it possible to add a setting that ignores the file not existing? There's
> already something similar for when the file is blank...
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
