tag:help.appveyor.com,2012-11-13:/discussions/questions/299-problems-configuring-build-artifiactsAppVeyor: Discussion 2018-08-25T01:46:55Ztag:help.appveyor.com,2012-11-13:Comment/332140152014-05-31T18:40:07Z2014-06-01T11:14:53ZProblems configuring build artifiacts<div><p>I'm trying to setup one of my projects to store build artifacts
but haven't been successful.</p>
<p>I want files from several different directories to be bundled
into a single zip file. For example, the following 3 DLLs should
all be bundled into a project.zip</p>
<p>src\project1\bin\Release\project1.dll<br>
src\project2\bin\Release\project2.dll<br>
src\project3\bin\Release\project3.dll</p>
<p>I have tried different variations for a wildcard pattern for the
build artifact path, but nothing seems to work. The most recent
pattern is "src/**/bin/$(configuration)". Is this possible and, if
so, what am I missing?</p></div>Scott Dormantag:help.appveyor.com,2012-11-13:Comment/332140152014-05-31T19:04:21Z2014-05-31T19:04:37ZProblems configuring build artifiacts<div><p>Well, automatic packaging is either pushing a single file as
artifact or pushing entire folder as a zip.</p>
<p>If you need to push several files as a zip I'd use
<code>7z</code> (which is already in PATH) and then
<code>appveyor.exe</code> command-line or PS cmdlet to push archive
to artifacts: <a href=
"http://www.appveyor.com/docs/build-agent-api#push-artifact">http://www.appveyor.com/docs/build-agent-api#push-artifact</a></p></div>Feodor Fitsnertag:help.appveyor.com,2012-11-13:Comment/332140152014-05-31T21:31:19Z2014-06-01T11:14:54ZProblems configuring build artifiacts<div><p>Ok. That makes sense. It would be nice if I didn't have to do it
through script but as long as that's available to me I should be
ok. It sounds like the alternative then would be to have 3 build
artifacts, one for each separate DLL.</p>
<p>Is it possible to have one build artifact has a wildcard "group"
for extensions? That would let me do something like this:</p>
<p>src\project1\bin\Release\project1.[dll|pdb|xml]</p>
<p>That would allow me to ensure that I only pick up those 3 files
from the bin directory rather than everything. I'm pretty sure I
could do this as separate build artifacts, but in my case that
would mean a total of 9 artifacts and any time I add a new project
I would be adding 3 artifacts.</p></div>Scott Dormantag:help.appveyor.com,2012-11-13:Comment/332140152014-05-31T21:36:53Z2014-06-01T11:14:54ZProblems configuring build artifiacts<div><p>Actually, would defining the build artifacts like this work?
(See attached file.)</p></div>Scott Dormantag:help.appveyor.com,2012-11-13:Comment/332140152014-05-31T22:02:25Z2014-05-31T22:02:25ZProblems configuring build artifiacts<div><p>Yeah, it should work. Let me know if it doesn't.</p>
<p>For <code>[dll|pdb|xml]</code> I think we could just support
regex, because glob syntax is something limited. You'll be able to
define path like <code>/your_regex_here/</code>.</p></div>Feodor Fitsnertag:help.appveyor.com,2012-11-13:Comment/332140152014-06-01T03:42:10Z2014-06-01T11:14:55ZProblems configuring build artifiacts<div><p>That sort of worked. Actually, it did work but I ended up with
multiple copies of the DLLs as build artifacts due to the fact that
there are cross-project references. I ended up using an "on build
success" script which used 7z to create the archive.</p>
<p>Yes, supporting regex rather than a glob syntax would be better.
That would provide the most flexibility.</p></div>Scott Dormantag:help.appveyor.com,2012-11-13:Comment/332140152014-08-06T21:04:15Z2014-08-06T21:04:15ZProblems configuring build artifiacts<div><p>Any updates on this request?</p></div>Scott Dormantag:help.appveyor.com,2012-11-13:Comment/332140152014-08-07T01:32:22Z2014-08-07T01:32:22ZProblems configuring build artifiacts<div><p>Haven't started yet, but don't think it's going to be hard to
implement.</p></div>Feodor Fitsner