Improved instructions for getting artifact builds from try server
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 35/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Stale
- Domain
- build-system, documentation
Research direction
Read the existing artifact-builds and try-server instructions at the two developer.thunderbird.net links, then compare them with issue #99 and the Bugzilla reference. Update the relevant documentation with the draft Treeherder steps for Windows, Linux, and macOS downloads, and verify that the instructions cover downloading and installing a completed try build.
Written by the indexing model from the issue text.
Description
Ben and I had an exchange about having instructions that could be used by educated users for using try builds for testing patches - but the current instructions are incomplete. References:
- issue #99
- https://developer.thunderbird.net/thunderbird-development/building-thunderbird/artifact-builds
- https://developer.thunderbird.net/thunderbird-development/fixing-a-bug/try-server#get-an-installable-build-from-a-try-run
- https://bugzilla.mozilla.org/show_bug.cgi?id=399475#c29
Draft of instructions might look like:
When the build at https://treeherder.mozilla.org/jobs?repo=try-xxxxxxxxxx is complete (normally takes xx hours)
- Click the green "B" (for binary) next to one of the following: "Windows 2012 x64 opt", "Linux x64 opt", "OS X Cross Compiled shippable opt" (unless instructed to use a debug build)
- In the black header below click "Artifacts and Debugging"
- In the Artifacts section, to download the install file click on target.installer.exe (Windows), target.tar.bz2 (Linux), or target.dmg (Mac)
- Install the downloaded file
- Dominant language
- No language data
- Stars
- 114
- Forks
- 86
- Avg merge
- 2h 37m
- Merged PRs (30d)
- 1
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from thunderbird/developer-docs
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
thunderbird/developer-docs#244 · 2 comments ·
-
Difficulty 1/5 1-3 hours Newbie friendliness 62/100
thunderbird/developer-docs#125 ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
thunderbird/developer-docs#238 · 6 comments ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 35/100
thunderbird/developer-docs#232 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
thunderbird/developer-docs#229 · 2 comments ·
All issues in thunderbird/developer-docs
Similar issues
-
type/automation type/tech-debt
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
priority: p3
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
googleapis/librarian#7636 ·
-
Bug v3
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
-
package-update
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
oSoWoSo/vOid_Community_repOsitory#147 · 1 comment ·
-
Builders
Difficulty 2/5 1-3 hours Newbie friendliness 72/100