-
-
Notifications
You must be signed in to change notification settings - Fork 290
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
ci: update electron-builder and Azure pipeline configurations #1404
Conversation
nsis-web target is not used
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
looks great!
@@ -21,9 +21,9 @@ jobs: | |||
steps: | |||
- checkout: self | |||
persistCredentials: true | |||
- task: NodeTool@0 | |||
- task: UseNode@1 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
consider using lts node version alias instead of the hardcoded one
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure if Azure supports the lts
value. The documentation only refers to semver values.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh, I forgot it's Azure. Perhaps it makes sense to migrate to GitHub CI
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agree that GitHub CI would be more convenient, though I'm guessing there was a reason why Azure was originally selected. Maybe the machines are more powerful? It's also used in other Appium projects (e.g. xcuitest driver).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
it was selected before github had any CI. Yes, it is still used, although not by xcuitest driver. It's used in webdriveragent because of the high amount of e2e tests we run there and the limited capability of free macOS-based runners on Github. Otherwise I would also migrate them.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Perhaps I tried to convert this project to GHA before. Then, I needed maybe Window's signature which probably needed Dan's help. We could restart migrating them.
…#1404) * ci: update azure VM images * ci: update Node for Azure * ci: always publish in x64 and arm64 * ci: move electron-builder config into own file for clarity * ci: remove electron-builder nsisWeb option nsis-web target is not used * ci: slightly adjust common package options * ci: remove electron-build filepaths already included by default * ci: use common artifact name format * ci: omit repeating default paths to app icon * ci: build separate artifacts for both mac architectures * ci: add tar.gz target for Linux * ci: add entitlements file for mac signing * chore: fix syntax for Azure UseNode task
This PR updates the configuration for
electron-builder
(which generates OS-specific application packages) and the Azure pipeline that is triggered during the release process (which is whereelectron-builder
is run):electron-builder
config to a separate file for clarityx86_64
suffix instead ofx64
tar.gz
artifacts for LinuxAs a result of these changes, I believe the number of generated artifacts will now increase to 26.
Resolves #1400.