I mean how to get the assembly in place, now I 'only' need to compile project b successfully.
Den tirsdag den 18. december 2012 16.46.55 UTC+1 skrev Kenneth Nielsen: > > figured it out my self. ;-) > > Den tirsdag den 18. december 2012 16.37.47 UTC+1 skrev Kenneth Nielsen: >> >> Hi all, >> >> I have a job building a C# assembly named 'a.dll', when I succeed with >> the build, I have Archive the artifacts a.dll and a.pdb for use in another >> job named b. >> job a - post build step >> ¤ Archive artifacts. >> Files to archive: a.* >> >> In b I have a copy artifacts task from another project setup as my first >> build step. I want to place the a.dll in a folder relative to b, so i will >> compile, but I never get the a.dll anywhere. (It is happening on the same >> slave.) >> job b - first build step >> ¤ Copy artifacts from another project >> project name: job a >> which build: latest sucessfull >> stabel build only - unchecked >> articfacts to copy: a.dll;a.pdb >> target directory: ./src/release/ >> flattern directories and optional are both unchecked. >> >> on the build slave I get the folders correct under jenkins/workspace/job >> b, but I don't get the assemblies in the ./src/release folder so I can >> compile (the release build) Any clues why? >> >> Should I use the fingerprint plugin to get it to work ? and why? >> >> thanks >> Kenneth >> >> >> >> >>
