(From http://stackoverflow.com/questions/2470008/how-do-you-prevent-a-hudson-slave-from-archiving-artifacts)

It turns out our slaves spend a considerable amount of time moving the archived artifacts back to the master Hudson node. It at least triples the duration of the build. It would be nice if there would be a way to prevent it. However, setting the maximum number of builds to keep doesn't have an influence at all. Is there another way to prevent sending the results back to the central Hudson master?

Note that I actually don't have the archive artifacts option checked. However, the slave is still 'archiving' whatever it finds to the master:

[HUDSON] Archiving .../pom.xml to .../pom.xml
[HUDSON] Archiving .../...-0.1.3-SNAPSHOT.jar to .../...-0.1.3-SNAPSHOT.jar

... with the second path in every line always being a location on the master. Is this a bug? Is there a workaround?