On Thu, Aug 16, 2012 at 10:45 AM, Martin d'Anjou <martin.danjo...@gmail.com> wrote: > Hi, > > When I promote an archived build while a build is running, the Copy > Artifact plugin overwrites the running build artifacts with the > archived ones. How should I configure the Build Promotion and the Copy > Artifact to avoid this problem?
What are you trying to achieve? Are these artifacts required for a build. For example, Jenkins Job #1 produces a jar that's required for Job #2. You want to copy over this jar, but only when you "promote" it. We use a Maven repository for archiving these artifacts which avoids the issue. When we promote Job #1, it deploys the jar into our Maven repository. When Job #2 runs, it uses Ivy or Maven to pull the artifact into its build process. 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). -- David Weintraub qazw...@gmail.com
