Build:Release Automation: Difference between revisions

Build:Release Automation (view source)

758 bytes removed , 5 October 2007

bug sections merged into current status, put enhancements under outstanding issues

canmove, Confirmed users

1,511

edits

@@ Line 353: / Line 353: @@
 =Production changes=
 ==Staging/Production Buildbot master differences==
@@ Line 360: / Line 359: @@
 # Bootstrap - prod pulls tag e.g. RELEASE_AUTOMATION_M5, staging pulls tip ''ok''
-==Outstanding issues==
+=Outstanding issues=
 # How to handle bootstrap logs.. remove them between runs? Don't want accumulation on slaves ''remove at start''
@@ Line 366: / Line 365: @@
 # "Source" and "Staging" steps - install a buildslave on stage, or stage everything on build-console? ''use build-console''
 # Make sure QA checks e.g. top 5 extensions after Mac Intel switch
-=Caveats=
-==Bugs==
-* <strike>([https://bugzilla.mozilla.org/show_bug.cgi?id=394963 bug 394963]) Need to use cvs (in master.cfg) from ShellCommand to make sure that we always use the proper bootstrap tag</strike>
-* <strike>(needs bug filed) "scp -r" does not work on pacifica-vm; needed for l10n</strike> fixed in tinderbox
-* <strike>{{bug|396438}} bootstrap needs to automatically sync with stage</strike>
-* <strike>([https://bugzilla.mozilla.org/show_bug.cgi?id=394034 bug 394034]) in private repos, in /mofo/release/stage/firefox-src-tarball-nobuild, there is a script that is called in the "source" step. Has hardcoded CVSROOT which needs to be updated to use ":ext:cltbld@staging-build-console.build.mozilla.org:/builds/cvsmirror/cvsroot"</strike>
 ==Enhancements==