|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
NOTE: While doing some ad-hoc testing to reduce this bug to the most basic use case I noticed something even stranger about the play between these two plugins. If you have two post-build operations, one using a typical artifact deployer configuration (ie: with no conditions on it) and another one that combines both to conditionally deploy other artifacts, when you go back to delete the test build neither of the artifacts gets purged.
However, if you take the job exactly as-is and simply remove the post-build step that uses the Flexible Publisher, then the other step that does a simple artifact deployment does work as expected. It's almost as if as soon as the job encounters an instance of the flexible publisher anywhere in the post-build steps, it affects the behavior of the artifact deployer - whether it actually uses the flexible publish or not.