MozillaWiki

ReleaseEngineering/BuildFaster: Difference between revisions

Page Discussion

ReleaseEngineering/BuildFaster (view source)

Revision as of 21:36, 8 November 2012

1,497 bytes removed ,  8 November 2012
→‎Current activities
 
(6 intermediate revisions by the same user not shown)
Line 39: Line 39:
| Move all Linux builds to AWS  
| Move all Linux builds to AWS  
| jhopkins
| jhopkins
| {{StatusHealthy|status=Already have b2g building on AWS, just need mock environments for other Linux builds.}}
| {{StatusHealthy|status=All Firefox builds are there now, just waiting on Thunderbird to catch-up.}}
|-
| {{bug|623617}}
| Derecursify the build system
| joey
| {{StatusBlocked|status=Joey and gps (and possibly mwu) should collaborate here to get Joey unblocked.}}
|-
| {{bug|593585}}
| Use pymake by default on Windows
| joey
| {{StatusBlocked|status=Lots of blockers that need tackling. May need to reassign some of these to Joey too.}}
|-
| {{bug|634746}}
| TBuild
| coop
| {{StatusHealthy|status=Underway}}
|-
|-
| {{bug|758624}}
| {{bug|758624}}
| Purchase new machines for win/linux testers that are not tied to aggressive obsolescence schedule
| Purchase new machines for win/linux testers that are not tied to aggressive obsolescence schedule
| coop
| coop
| {{StatusBlocked|status=Underway, evaluation nodes need setup. No people available yet due to Win8/10.8 setup.}}
| {{StatusBlocked|status=Underway. Various test OSes are being setup and validated.}}
|-
| ??
| Use sdwilsh's notification bot to help devs more easily watch the tree
| harth
| {{StatusHealthy|status=Mostly ready, needs polish, harth taking over}}
|-
|-
| ??
| {{bug|784913}}
| Profile mochitest plain
| migrate linux xpcshell testsuite to AWS
| jgriffin
| jmaher
| {{StatusHealthy|status=COMPLETE}}
| {{StatusBlocked|status=Blocked on panda work}}
|-
|-
| n/a
| {{bug|784913}}
| Get data on test run time for each of the moth individual tests
| migrate linux xpcshell testsuite to AWS
| ctalbert
| '''unowned'''
| {{StatusHealthy|status=COMPLETE}}
| {{StatusBlocked|status=Needs an owner}}
|}
|}


== Long Term Ideas ==
== Long Term Ideas ==
* {{bug|657738}} - Automatically determine when oranges happen and auto-star them (no owner/decision on steps yet)
* {{bug|657738}} - Automatically determine when oranges happen and auto-star them (no owner/decision on steps yet)
* {{bug|630534}} - (related) Host tree status outside of tinderbox
* Windows builds on AWS are still too slow, but we can revisit this regularly
** This would help us move away from tinderbox and would free up many of the constraints we currently operate under
* Cross-compile Mac builds on AWS
* Analyze using VMs for "dial-up" capacity
** after legal review, *yes* we think we can do this. Need to find a developer owner to give this a try.
** <s>Would need engineering resources to debug oranges that occur only on vms
* {{bug|772579}} - Can we run unittests on AWS for Linux (and eventually Windows)?
** Would need to run some low numbers of vms on an ongoing basis so that we continue to ensure they are providing results we can trust
** We may need to solve {{bug|617763}} so that these machines can be kept up to date (whether they live in the build VPN or not, i.e. if we use EC2 or something like that...).  Either way we must address the problem that they could be out of date between one dial-in and another dial-in.</s>
** this has been mostly solved by releng now in AWS, providing much higher capacity for building when required:
*** b2g is already building on AWS
*** {{bug|772446}} - need mock environments for other Linux builds: desktop (32- & 64-bit), Android*
*** Windows builds on AWS are still too slow, but we can revisit this regularly
*** Can we cross-compile Mac builds on AWS? Are there legal issues with doing so? I would love to be out of the hardware game for build/try entirely.
*** {{bug|772579}} - Can we run unittests on AWS for Linux (and eventually Windows)?
* Analyze methods of understanding and optimizing what we run on a per-checkin basis
* Analyze methods of understanding and optimizing what we run on a per-checkin basis
** Test code related to the current patch?
** Test code related to the current patch?
** Run full tests only every x pushes or y time (whichever occurs first).  Between those only run a set of tests related to the patch at hand. (Would need developer override and on-demand testing ability)
** Run full tests only every x pushes or y time (whichever occurs first).  Between those only run a set of tests related to the patch at hand. (Would need developer override and on-demand testing ability)
* less frequent debug builds
* less frequent debug builds
* use an optimized xpcshell + httpd.js to run debug tests (depends on {{bug|669953}})
* use an optimized xpcshell + httpd.js to run debug tests (depends on <s>{{bug|669953}}</s>)


= Data we need =
= Data we need =
Line 129: Line 101:


= Meetings =
= Meetings =
* [[ReleaseEngineering/BuildFaster/Meetings/2012-10-11|2012-10-11]]
* [[ReleaseEngineering/BuildFaster/Meetings/2012-06-28|2012-06-28]]
* [[ReleaseEngineering/BuildFaster/Meetings/2012-06-28|2012-06-28]]
* [[ReleaseEngineering/BuildFaster/Meetings/2011-10-26|2011-10-26]]
* [[ReleaseEngineering/BuildFaster/Meetings/2011-10-26|2011-10-26]]
ChrisCooper
canmove, Confirmed users
2,850

edits

Retrieved from "https://wiki.mozilla.org/Special:MobileDiff/449815...486184"