Thank you for the information. It seems that in my case (Jenkins 1.475), the "Archive the Artifacts" step only runs on successful builds, so I'm out of luck there.
For the time being I will use a hack (scp files to master!) and I'll look into modifying the copy-to-slave plugin, since it seems like the best fit for my use case. The other option, would be for me to modify the "HTML Publisher" plugin so it is slave-aware, since the "artifacts" I need to copy to the master, are HTML RSpec reports that I want to publish for end-users to view. That's probably the highest-value contribution I can make. Long term, I'm beginning to think about creating an RSpec formatter that outputs the JUnit XML format that Jenkins can parse; I'd like to experiment with Jenkins' ability to track the number of failing test cases over time, etc. Anyhow, just thinking out loud ... thanks again for giving me an avenue to explore. On Sunday, August 5, 2012 12:04:47 AM UTC-7, sti wrote: > > Yes, it is specific to that plugin. It is conventional for post-build > actions to run only if build is successful but some plugins that bring new > post-build actions allow you to configure the actions to run for failed > builds too. For example the Parameterized Trigger plugin is such. > > You could just use the archive artifacts setting to copy build outputs. > Jenkins always archives the matching files regardless if the build fails or > succeeds. That's what I do. > > -- Sami >
