Skip to content
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

Special behavior on test builds #42

Open
ItsHarper opened this issue Feb 12, 2017 · 1 comment
Open

Special behavior on test builds #42

ItsHarper opened this issue Feb 12, 2017 · 1 comment

Comments

@ItsHarper
Copy link
Owner

ItsHarper commented Feb 12, 2017

On startup, the user should be notified that this is a test build. It will not receive updates, and it should be deleted as soon as they are done testing whatever was being tested. Tell them that if this is the only version they have, they should download the official version from GitHub (provide link)

The test build should have access to the dev tools.

The build should have all auto update functionality disabled.

The dist npm script should be replaced with one that checks for a CI environment.

@ItsHarper
Copy link
Owner Author

ItsHarper commented Feb 20, 2017

An idea for this:

package.js should temporarily change the version number to include "test". The program can then detect that and behave accordingly. We should be very careful that even if the script ultimately fails, the version number will be switched back.

Set name in the packaging options to include "test", and check for that. electron/packager#602 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant