Navigation Menu

Skip to content

Instantly share code, notes, and snippets.

@escapewindow

escapewindow/fennec_relpro.md Secret

Last active March 4, 2017 01:30
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 1 You must be signed in to fork a gist
  • Save escapewindow/5819efb7bab47be9868c7375317efaae to your computer and use it in GitHub Desktop.
Save escapewindow/5819efb7bab47be9868c7375317efaae to your computer and use it in GitHub Desktop.
Download ZIP
Raw
fennec_relpro.md

2017-02-28

  • will need to uplift this patch to m-a, with kwierso's fix
  • fennec hook - we'll need this, or equivalent, in releasetasks. alternative is manually triggering via releaseduty. commented in bug 1338161
  • latest fennec candidates graph is green! task graph
    • patch pending r?
    • will need to land this on m-c and uplift to m-a
    • currently have the beetmover workers pinned to my puppet env for staging beetmover push-to-candidates; we'll need a real puppet patch for dev+release beetmover creds+bucket info
    • anyone want to take a look at these builds/uploads? I don't know where the staging bucket is browsable via http, if at all
    • hm, why are we pointing at 53.0-candidates instead of 53.0b1 ? should browser/config/version.txt say 53.0 or 53.0b1? should we be pointing at browser/config/version_display.txt ?
  • beetmover scriptworkers are a bottleneck; we'll need to spin some [2?] more up
  • i need to document any manual steps for releaseduty
  • still need to create a mozilla-beta l10n-bumper patch, and enable it before merge day monday, and document manual l10n-bumping for releaseduty

See Mihai's fork for the updates during his day.

2017-03-01

Overview: fennec is looking good, though we need some owners in the volunteers section below. The latest staging beta is here -- green, and the stage stage looks good :)

  • We should make sure to help Rail with all loose ends on the linux side - he thinks he's 90% sure he can get desktop done Thurs.
  • We should try triggering the initial releasetasks graph (source + fennec_candidates), and then the 2nd releasetasks graph (push candidates to releases, etc.) to make sure it all works end-to-end.

done

  • all new fennec deps should now be hanging off bug 1343393 now.
  • mtabara spun up 2 new beetmoverworker instances. We were bit by forgetting the gpg keys, but they're now working just fine. The new beta staging builds should be good, and we have a bus factor +1.
  • fixed beetmover version numbers - see el. However, it's unknown if we need to fix the beetmover version numbers for desktop, or turn off beetmover for desktop.
    • if we fix it, then we should have the version number be part of every beetmover task definition - beetmoverscript + in-tree patch
    • if we turn it off, we change the mozilla_beta_tasks target_task_method to skip all beetmover and checksum kinds.

to do - volunteers?

I'm willing to handle any of these, though testing the apks is tricky sans device. Might be easiest if we parallelize though.

(might be easiest to use/add cards in the trello board for these rather than forking this gist?)

  • filed a new trigger fennec builds from releasetasks bug. We have some ideas in there; we need to add a template or auto-updating hook and test. Not sure if we have an owner yet -- kmoir was looking, as was I.
  • actually install some of these apks - do they look like beta apks? any multi- or single-locale testing would be super helpful too... just verify they are localized at the very least
  • how do we test the 2nd releasetasks graph (candidates -> releases) ?

to uplift - ALL UPLIFTED

to do pre-beta1 - just a reminder

  • unpin beetmoverworker-* from aki's puppet env, once we're done with our fennec staging betas
  • start l10n-bumper on m-b, once it seems safe (this might be monday)
  • document manual tasks for releaseduty - ideally these should approach zero

2017-03-02

Overview

  • met w/ rail and mtabara to discuss fennec overview

  • discussed releasetasks graph1->candidates_fennec with kmoir in bug 1343649 and irc; looks like we're on the same page now

  • worst case, we could go-to-build for fennec today:

    • noop ship-it
    • skip source
    • kick off fennec_candidates hook
    • hack candidates to release script, run manually
    • run pushapk manually

    but we can get it even smoother with the ongoing tasks

  • we're in good shape, thanks team! let's finish strong

in progress

  • jlorenzo fixed the single locale repacks and tested the apks
  • kmoir is working on triggering the candidates_fennec decision task from the 1st releasetasks graph in bug 1343649 ; we seem to be back on the same page
  • mtabara is working on the 2nd releasetasks graph, which can reuse much of desktop's push-to-releases tasks and logic
    • also updating docs in releasewarrior; let's make sure anything we know about makes it here
  • we can land m-b l10n-bumper when we're ready to turn it on
  • turned off linux l10n on push on jamun; patch is pending r? and should land on m-c and m-a

questions:

  • unit- and talos- tests aren't triggering for linux on jamun; is that intentional? will we need to do something to turn those tests on on m-b?
  • anyone need help with anything?

carryover: to do pre-beta1 - just a reminder

  • unpin beetmoverworker-* from aki's puppet env, once we're done with our fennec staging betas
  • start l10n-bumper on m-b, once it seems safe (this might be monday)
  • document manual tasks for releaseduty - ideally these should approach zero

2017-03-03

Status, as of my EOD Friday:

staging work over the weekend

  • aki landed this patch which will have to be reverted on jamun to do another staging release
  • make sure the beetmoverworkers are pinned to aki's env if you run another staging release!

Merge day

Fennec go-to-build

Fennec push-to-releases

  • mtabara got this working!

Cleanup

  • get the above linux-nightly-tests and releasetasks-graph-1 working
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment