Rail/2010-02-01: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
mNo edit summary
Line 17: Line 17:
* Suggestion: Use separate repositories (or explicit/named branches) for staging and production configs. In this case diffing and merging tasks will be easier.  
* Suggestion: Use separate repositories (or explicit/named branches) for staging and production configs. In this case diffing and merging tasks will be easier.  
diff -urN mozilla2 mozilla2-staging > staging.patch; less staging.patch; patch < staging.patch; is stateless, while merging between repos/branches tracks all relations between staging and production areas.
diff -urN mozilla2 mozilla2-staging > staging.patch; less staging.patch; patch < staging.patch; is stateless, while merging between repos/branches tracks all relations between staging and production areas.
* Change Sources:
** buildbotcustom.misc.generateBranchObjects(config, name):
*** HgPoller
*** HgAllLocalesPoller (if enable_l10n is set)
** master-main.cfg:
*** PBChangeSource
** master2.cfg:
*** HgAllLocalesPoller for mozilla-1.9.1 and mozilla-1.9.2
*** HgPoller for mozilla-central and mozilla-1.9.2
** release_master.py:
*** FtpPoller ("post_signing" branch, searches for "win32_signing_build") triggers "partner_repacks", "l10n_verification" and "updates" Schedules
** mobile_master.py:
*** HgPoller (mobile-browser)

Revision as of 10:01, 1 February 2010

Infrastructure

  • Win32: ReferencePlatforms/Win32
    • Related bug and hg links
    • Q: Why to bore ourselves with firewall rules? Use an open firewall like in Linux...
  • Overall
    • Suggestion: Simplify ssh configuration by distributing `known_hosts' files or by using expect(1) scenarios.

Buildbot

  • Suggestion: Use separate repositories (or explicit/named branches) for staging and production configs. In this case diffing and merging tasks will be easier.

diff -urN mozilla2 mozilla2-staging > staging.patch; less staging.patch; patch < staging.patch; is stateless, while merging between repos/branches tracks all relations between staging and production areas.

  • Change Sources:
    • buildbotcustom.misc.generateBranchObjects(config, name):
      • HgPoller
      • HgAllLocalesPoller (if enable_l10n is set)
    • master-main.cfg:
      • PBChangeSource
    • master2.cfg:
      • HgAllLocalesPoller for mozilla-1.9.1 and mozilla-1.9.2
      • HgPoller for mozilla-central and mozilla-1.9.2
    • release_master.py:
      • FtpPoller ("post_signing" branch, searches for "win32_signing_build") triggers "partner_repacks", "l10n_verification" and "updates" Schedules
    • mobile_master.py:
      • HgPoller (mobile-browser)