How do you prevent a Hudson slave from archiving artifacts?
Posted
by Wilfred Springer
on Stack Overflow
See other posts from Stack Overflow
or by Wilfred Springer
Published on 2010-03-18T13:12:17Z
Indexed on
2010/03/18
13:51 UTC
Read the original article
Hit count: 174
hudson
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?
© Stack Overflow or respective owner