Search results

Jump to: navigation, search
Results 1 - 40 of 145
Advanced search

Search in namespaces:

  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  

Page title matches

Page text matches

  • :"What's the best way to install a new system?" ...manifests themselves are documented here. Any new modules should be added to the proper list below.
    18 KB (2,377 words) - 19:18, 4 June 2018
  • * [[ReleaseEngineering/How To|How Tos]] We ship Firefox to the world!
    15 KB (2,037 words) - 13:56, 11 March 2021
  • ...dev reports a problem pushing to hg (either m-c or try repo) then you need to do the following: ** If he doesn't respond, then escalate the bug to page on-call
    14 KB (2,223 words) - 02:33, 21 December 2018
  • {{Release Engineering How To|VCS Sync}} ...'s original purpose to being the tool used whenever "this repository needs to be publicly visible 'over here'", perhaps with modifications, and a few exc
    27 KB (4,119 words) - 02:12, 30 June 2018
  • ...support. The team's '''''responsibilities include''''' but are not limited to: * [[ReleaseEngineering/Buildduty_manifesto#Firefox_CI_infrastructure_outage_coordination_and_inves
    6 KB (839 words) - 13:44, 15 January 2019
  • {{admon/note|Add your photos!| Welcome to the Innovation Fair page from Summit 2013! Some booths don't have a photo, ...s team will be showing off the latest in web and browser development tools to anyone interested in hacking on web apps, add-ons or the browser itself.
    34 KB (5,433 words) - 22:24, 5 May 2023
  • ...ll go through the same tests as a mozilla-central push, and you'll be able to download builds if you wish. == Getting access to the Try Server ==
    18 KB (2,917 words) - 22:21, 5 March 2020
  • ...asters automatically update to the latest commit, and start deploying that to hosts. == Exceptions to Review Requirement ==
    18 KB (2,907 words) - 19:18, 4 June 2018
  • Mercurial is one of our core binaries that we need to install everywhere. ...due to wanting a single, common, place for mercurial, and to avoid needing to update system packages that may depend on mercurial.
    14 KB (2,077 words) - 15:37, 12 December 2017
  • ...ntributing to a large and complex codebase, but we’ve prepared some tips to help you fix a good-first-bug and land a patch in Firefox. ...#addons room (see [[Matrix]]). For a general overview of how to contribute to Firefox, please [https://firefox-source-docs.mozilla.org/contributing/contr
    13 KB (1,973 words) - 12:10, 10 May 2022
  • ...team]] where sheriffs respond to Firefox code regressions, CiDuty respond to the infrastructure that builds and tests Firefox code. ...%20Operations&component=CIDuty CIDuty] component if you are not sure where to file your CI related ticket
    3 KB (446 words) - 15:09, 15 January 2019
  • {{Release Engineering How To|Setup a Personal Development Master}} ...call it directly with: <pre>python /tools/misc-python/virtualenv.py </path/to/destination></pre>
    16 KB (2,473 words) - 14:44, 21 November 2017
  • ...ad-hoc tools for packaging the tools we build with, but there is an effort to make these packages generic and redistributable. ...second contains specfiles that are more generic and have tooling in place to make building the packages a lot easier.
    3 KB (496 words) - 21:38, 16 March 2012
  • {{Release Engineering How To|Connect and Troubleshoot workers in CI}} = How to add/define a worker if it is missing from Taskcluster =
    4 KB (707 words) - 00:44, 16 April 2019
  • In the A-team we have recently been focusing on making mozharness easier to use by developers and give more flexibility in its use. ...ly started with Release Engineering and the A-team has been able to use it to contribute on the side of test jobs.
    15 KB (2,200 words) - 13:44, 13 February 2018
  • ...elopment process is open and participatory, new developers can gain access to some of the most skilled and experienced developers in the industry. Workin ...be confusing. A typical path for beginners to learn how to code Mozilla is to start by making extensions. Writing an extension in JavaScript, then writin
    8 KB (1,155 words) - 20:49, 9 July 2009
  • This makes it harder for newcomers to work on a tool, and increases the likelihood that a bug or problem in one t It's not ironclad, and is subject to change by consensus.
    9 KB (1,391 words) - 19:27, 27 April 2018
  • Welcome to CiDuty! ...nsuring they have access to the appropriate systems that they are expected to use.
    12 KB (1,935 words) - 15:07, 15 January 2019
  • ** returning re-imaged slaves to production * handling [[ReleaseEngineering:Buildduty:Nagios|nagios alerts]] for slaves
    10 KB (1,633 words) - 10:52, 23 April 2019
  • ...all puppetmasters in case one is down. It takes an optional ''$homedir'' to specify the user's homedir, with the default being in ''/home''. This defi .../How To/Install a Python Virtualenv with Puppet]] for a tutorial reference to using the module.
    3 KB (387 words) - 22:29, 13 August 2012

View (previous 20 | next 20) (20 | 50 | 100 | 250 | 500)