-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
S3 won't upload app files #1331
Comments
Please try 15.1.1 |
@develar After updating I got the same behaviour. Logs show activity like if the file was being uploaded but there is nothing in the bucker, just the files I mentioned before. |
@bilby91 Hmm... it works for me. Ok, I will try exactly as you do |
Do you build on macOS? |
@develar Will try with |
@develar Same with |
Is it possible to provide your config? |
And please set env DEBUG=electron-builder and attach log of the terminal output. |
Sure, let me prepare the config and run the command with the |
@develar Here is the missing information https://gist.github.com/bilby91/157655a4871a1c687e9a88e6c9caf42c Thanks! |
@develar Any thought on what is happening ? Maybe you can point me to the appropriate peace of code and I can debug it. |
@bilby91 I suspect that aws sdk doesn't like our progress stream. I am going to use aws sdk progress API instead of general handler. Probably I will do it today/tomorrow. BTW, please ensure that you use electron-publisher-s3 15.0.1 |
@develar I just verified that is not working for |
No. Works for me. In any case it is better to use Also, you can try to build app on CI server (e.g. Travis). |
You can check using my sample project:
|
@develar Sure, let me try. |
@develar Same happen with your sample project. Only |
@develar If I provide a custom path it seems to be working! I'm going to check in my application now. |
@bilby91 Nice. I will check this case. |
@develar It's more strange now :(. It worked for your sample app if I changed the bucket path, didn't work on my application with the same publishing configuration. UPDATE
|
same issue here, only json files were uploaded |
Sorry that this critical issue is not yet fixed. I really hope to fix it on this weekend. |
@develar can you please point where to look for this issue in code? |
@mediaslav https://github.com/electron-userland/electron-builder/blob/master/packages/electron-publisher-s3/src/s3Publisher.ts In any case we must use aws sdk progress API instead of our generic implementation. It should be fixed before investigating this issue. |
After updating Work you are planning in the weekend can solve this too ? Thanks! |
Looks like its common problem with uploading big files to S3, and best way is to use multipart uploads with retry on error. Maybe it makes sense to use lib like https://github.com/faceleg/node-s3-client/ for that |
@mediaslav I was hoping that AWS-SDK doesn't *** in the latest versions, but it seems you are right. Thanks for the link to updated s3 client. |
@mediaslav @develar Makes a lot of sense based on the behaviour I'm having! It was like my internet connection got totally broken when I published my artifacts :( |
Awesome! Will try it out! |
@develar When could we expect a new release ? |
@bilby91 In 3 seconds, 16.6.2 ( |
🙌🏻 |
@develar the release does not seem to be on npm yet, is it published somewhere else? Big thanks for fixing this btw! 👍 |
@Maddoc42 It is |
@develar thanks, that worked :) |
Hello,
I'm trying to make the publishing feature work in our project but I'm not sure if I understood correctly the behaviour.
We are building application for mac, win and linux. We are using S3 as the publishing provider.
From my understanding, after I run
npm run release
(setuped asbuild -mwl --publish always
) I expect to have all the packaged files on the specified bucket in S3. The thing is, onlylatest-mac.json
andlatest.yml
are published to S3. I'm missing the dmg, exe and AppImage files.I'm doing something wrong or maybe there is something I'm not understanding.
Any help is more than welcome! Thanks and this project rocks!
Versions:
electron-builder 15.1.1
electron-publisher-s3 15.0.1
Status
path
is set.yarn
instead ofnpm
and didn't workedThe text was updated successfully, but these errors were encountered: