forked from appium/appium-desktop
-
Notifications
You must be signed in to change notification settings - Fork 1
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
Set up CI with Azure Pipelines #2
Open
azure-pipelines
wants to merge
156
commits into
master
Choose a base branch
from
azure-pipelines
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…itor. empty window for now
* Add check-engine to package-ci script * Require NPM 3 -> 4 and Node 6 -> 7 * This is to prevent problems we had when using newer versions of NPM/Node * Since this isn't a package that is published to NPM and is not ever imported as a dependency, having strict constraints isn't a big problem * Fix e2e because it uses nested node_modules when using shrinkwrap
* Use request to check if updates available * Native autoUpdater downloads updates automatically * We want to be able to check if updates are available first * So, make a call to /update endpoint directly and pass in the version to check if there's an update available * Redo autoupdater * Use the native electron dialogs instead of using a custom React workflow * Right now it automatically downloads it * Next step will be to check for availability first before proceeding to download * Show message if no updates available
dpgraham
force-pushed
the
azure-pipelines
branch
from
September 19, 2018 23:03
2b429fe
to
cac930b
Compare
dpgraham
force-pushed
the
azure-pipelines
branch
from
September 24, 2018 21:04
1db8624
to
e6afbae
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.