Base stream of PartialWrapperStream must be seekable

radekz's Avatar


24 May, 2019 04:56 PM

When trying to deploy zipped artifact to Elastic Beanstalk Environment (using Environment) I receive

...environment 'mywebsite-dev' found and available for redeployment.
...starting redeployment to AWS Elastic Beanstalk environment 'mywebsite-dev'
...making sure upload bucket 'elasticbeanstalk-us-east-1-xxxxxxxxxxxx' exists
....uploading application deployment package to Amazon S3
......uploading from file, size 69229160 bytes
Base stream of PartialWrapperStream must be seekable

I've obfuscated names of envrionment and bucket etc.

Zip package is created as part of a build command:

zip -r . -x \*.git\* \*puphpet\* \*.node_modules\* composer* Vagrantfile \*codebuild-images\* \*self_signed_ssl\* gulpfile.js

  1. 1 Posted by Ilya Finkelshte... on 24 May, 2019 07:02 PM

    Ilya Finkelshteyn's Avatar

    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.

    Please let us know if you can do this experiment and how it goes.

  2. 2 Posted by radekz on 27 May, 2019 01:02 AM

    radekz's Avatar

    Thanks for your reply

    Under Envronment I've changed clone directory to ~/build

    Then under Artifacts I've specified ~/build under Path to Artifact

    Now I get

    Collecting artifacts... No artifacts found matching '~/build' path

    I'm attaching my AppVeyor.yml

  3. 3 Posted by Ilya Finkelshte... on 27 May, 2019 10:13 PM

    Ilya Finkelshteyn's Avatar

    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 cd command). We also call it "build folder".

    When you set path in artifacts setting, AppVeyor treats it as a relative path inside the build folder. Obviously there are no ~/build folder inside the build folder, which is ~/build itself. This is the reason you are getting No artifacts found warning and no artifacts were created.

    What I recommend is:

    • do not set custom clone directory (it does not affect artifact packaging)
    • create some folder, for example ebs-package-dev in the current build directory during the build.
    • copy all needed files (the ones you added to the zip file before) to the folder as a final step in your script
    • set this folder (ebs-package-dev in our example) as an artifact path
  4. Ilya Finkelshteyn closed this discussion on 28 Jul, 2019 09:01 PM.

Comments are currently closed for this discussion. You can start a new one.

Keyboard shortcuts


? Show this help
ESC Blurs the current field

Comment Form

r Focus the comment reply box
^ + ↩ Submit the comment

You can use Command ⌘ instead of Control ^ on Mac