-
-
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
How to build in a dev environment without publishing credentials #2670
How to build in a dev environment without publishing credentials #2670
Comments
Publish is not performed automatically on local machine, only if CI detected. Maybe you pass |
@develar I've tried running the command with |
Please set env |
Here it is:
|
Hi Igor, I just ran into something similar and resorted (for now) to setting
as a temp workaround. HTH. |
@cweekly thanks for your message. Unfortunately, this is not an option for us. Our publishing is being done through |
@develar It seems like the problem is that publishing is being triggered for whatever reason. I don't understand why since I'm not on a tagged commit and neither on CI. What could be triggering a publishing other than those reasons or by using |
Bug. Will be fixed evening CET. Thanks for log. |
We need to compute final effective publish configuration for update info files, because we generate it ALWAYS. Why always? Because some users don't use our publisher and give a freedom. Why S3 needs AWS credentials to compute effective configuration? Because S3 bucket URL depends on bucket on region (don't ask why :() |
So, will be allowed to build without AWS credentials, but, obviously, app-update.yml in the app resources will be not always correct. As you need it for dev builds, it is ok. |
yeach... your bucket name is dotted — |
The command
$ electron-builder build
fails on a development environment because we are not providing AWS publishing credentials on local environments.The error being thrown is
CredentialsError: Missing credentials in config
.Is there any way to build/package the app locally just for testing purposes without having to provide publishing credentials?
The text was updated successfully, but these errors were encountered: