-
-
Notifications
You must be signed in to change notification settings - Fork 655
MakingAutomatedBuilds
The following information is for NVDA committers and details how to trigger the creation of automated builds that can be tested by users.
Snapshots are automatically built once each day for a predefined list of branches and made available on the [wiki:Snapshots] page. However, if you need to trigger a build, you can do this by using the nvdaSnapshot command from the shell on pebi.nvaccess.org. You may wish to run it with the -v option so you have some idea of its progress.
You can create one-off builds of any local branch for users to test. This is done by pushing to the NVDA try Git repository. To make this easier, you should first create a Git remote:
git remote add try git.nvaccess.org:/srv/git/nvdaTry.git
You can then push your working branch to make a try build:
git push try myWork
After the build completes in a few minutes, you will be sent an email with the status of the build and, if successful, download URLs. The email address used will be the email address of the last committer, so if you weren't the last committer, you should make an empty commit before pushing:
git commit --allow-empty -m "Try"
Note that branches pushed to the try repository are temporary and are removed as soon as the build is complete, so you still need to push them somewhere else if you want others to be able to access the commits.
- FAQ
- Application Support
- Connect
- Guides
- Extra Voices
- Log Files And Crash Dumps
- Log Levels (move to userguide / delete?)
This section will be moved to the NVDA repository as a priority
- Internals
- Notes Adding support for aria attributes to browsers
- Using COM with NVDA and Microsoft Word