> > Another possibility is to copy the artifacts not to the build > directory itself, but to a directory outside of Jenkins (which is > pretty much what the Maven repository does for us). > > Well, I think what I am trying to achieve is simple: promote a build while another build is running on the same project. The artifact names are the same at each run, so the file names collide on the file system in the workspace during the promotion. Note that I clean up the workspace at the beginning of each new run of the job with rm -rf * because I want a clean slate when the job begins. Like you said, to solve the problem, I cannot copy the promoted build artifact into the current workspace, I need to copy it to an absolute path elsewhere. This is what I have done. It is an annoying workaround, I wish Jenkins promoted builds had their own workspace.
BTW I am not using Jenkins for a Java flow, so Maven does not apply to my case (and nor does any open source flow for that matter). I am happy that bare bones Jenkins is development flow agnostic and I hope it stays this way. Cheers, Martin
