Ulli Hafner created JENKINS-12692:
-------------------------------------

             Summary: Plugin destroys configuration of Publishers
                 Key: JENKINS-12692
                 URL: https://issues.jenkins-ci.org/browse/JENKINS-12692
             Project: Jenkins
          Issue Type: Bug
          Components: flexible-publish
            Reporter: Ulli Hafner
            Assignee: bap
            Priority: Blocker


After installing the flexible-publish plugin, the Publishers of some jobs get 
corrupted on save. 

E.g. I have a WarningsPublisher in my job with the following serialization:
{code}
<publishers>
    <hudson.plugins.warnings.WarningsPublisher>
      <healthy></healthy>
      <unHealthy></unHealthy>
      <pluginName>[WARNINGS] </pluginName>
      <defaultEncoding></defaultEncoding>
      <canRunOnFailed>false</canRunOnFailed>
      <useDeltaValues>false</useDeltaValues>
      <thresholds>
        <unstableTotalAll></unstableTotalAll>
        <unstableTotalHigh></unstableTotalHigh>
        <unstableTotalNormal></unstableTotalNormal>
        <unstableTotalLow></unstableTotalLow>
        <failedTotalAll></failedTotalAll>
        <failedTotalHigh></failedTotalHigh>
        <failedTotalNormal></failedTotalNormal>
        <failedTotalLow></failedTotalLow>
      </thresholds>
      <shouldDetectModules>false</shouldDetectModules>
      <dontComputeNew>true</dontComputeNew>
      <parserConfigurations/>
      <consoleLogParsers>
        <string>Java Compiler</string>
      </consoleLogParsers>
    </hudson.plugins.warnings.WarningsPublisher>
{code}

After installing the flexible-publish plug-in, I get the following result when 
saving the configuration. Seems that there is an interaction between these 
plug-ins.  
{code}
<publishers>
    <hudson.plugins.warnings.WarningsPublisher>
      <healthy></healthy>
      <unHealthy></unHealthy>
      <thresholdLimit>low</thresholdLimit>
      <pluginName>[WARNINGS] </pluginName>
      <defaultEncoding></defaultEncoding>
      <canRunOnFailed>false</canRunOnFailed>
      <useDeltaValues>false</useDeltaValues>
      <thresholds>
        <unstableTotalAll></unstableTotalAll>
        <unstableTotalHigh></unstableTotalHigh>
        <unstableTotalNormal></unstableTotalNormal>
        <unstableTotalLow></unstableTotalLow>
        <failedTotalAll></failedTotalAll>
        <failedTotalHigh></failedTotalHigh>
        <failedTotalNormal></failedTotalNormal>
        <failedTotalLow></failedTotalLow>
      </thresholds>
      <shouldDetectModules>false</shouldDetectModules>
      <dontComputeNew>true</dontComputeNew>
      <parserConfigurations/>
      <consoleLogParsers>
        <string>Java Compiler</string>
      </consoleLogParsers>
    </hudson.plugins.warnings.WarningsPublisher>
{code}


I have no idea what is causing that problem. Maybe the reason is something deep 
in core or in my analysis plug-ins. I need to attach a debugger to our server...

Any ideas? What exactly is the flexible publisher doing in Jenkins core? Is it 
intercepting the publishers somehow?

Interestingly, the problem has been reported with another simpilar plug-ins 
too: the template project. 

Here some related issues: JENKINS-8185, JENKINS-12812.


--
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

        

Reply via email to