thunderbird / thunderbird/developer-docs

Improved instructions for getting artifact builds from try server

Open
#206 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
No language data
Stars
114
Forks
86
Avg merge
2h 37m
Merged PRs (30d)
1

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:

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

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

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.

Assessment

Domain
build-system, documentation
Issue type
Documentation
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.