tag:help.appveyor.com,2012-11-13:/discussions/problems/23754-base-stream-of-partialwrapperstream-must-be-seekableAppVeyor: Discussion 2019-07-28T21:01:13Ztag:help.appveyor.com,2012-11-13:Comment/472954532019-05-24T19:02:24Z2019-05-24T19:02:24ZBase stream of PartialWrapperStream must be seekable<div><p>This error can be related to the way archive were created. Is there any way you can put all what you need to be packaged into some folder and then set path to this this folder as an artifact in AppVeyor? AppVeyor then will zip the folder when creating an artifact. Then try to deploy it.</p>
<p>Please let us know if you can do this experiment and how it goes.</p></div>Ilya Finkelshteyntag:help.appveyor.com,2012-11-13:Comment/472954532019-05-27T01:02:58Z2019-05-27T01:02:58ZBase stream of PartialWrapperStream must be seekable<div><p>Thanks for your reply</p>
<p>Under Envronment I've changed clone directory to <code>~/build</code></p>
<p>Then under Artifacts I've specified <code>~/build</code> under Path to Artifact</p>
<p>Now I get</p>
<p><code>Collecting artifacts... No artifacts found matching '~/build' path</code></p>
<p>I'm attaching my AppVeyor.yml</p></div>radekztag:help.appveyor.com,2012-11-13:Comment/472954532019-05-27T22:13:59Z2019-05-27T22:13:59ZBase stream of PartialWrapperStream must be seekable<div><p>Clone directory is the one AppVeyor clones source code to, and it is also a current folder for all commands executed during the script (unless you run some <code>cd</code> command). We also call it "build folder".</p>
<p>When you set <code>path</code> in <code>artifacts</code> setting, AppVeyor treats it as a <strong>relative</strong> path inside the build folder. Obviously there are no <code>~/build</code> folder inside the build folder, which is <code>~/build</code> itself. This is the reason you are getting <code>No artifacts found</code> warning and no artifacts were created.</p>
<p>What I recommend is:</p>
<ul>
<li>do not set custom clone directory (it does not affect artifact packaging)</li>
<li>create some folder, for example <code>ebs-package-dev</code> in the current build directory during the build.</li>
<li>copy all needed files (the ones you added to the zip file before) to the folder as a final step in your script</li>
<li>set this folder (<code>ebs-package-dev</code> in our example) as an artifact <code>path</code></li>
</ul></div>Ilya Finkelshteyn