Closed Bug 642536 Opened 14 years ago Closed 14 years ago

New project branch request: ux

Categories

(Release Engineering :: General, defect, P3)

All
Other

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: limi, Assigned: lsblakk)

References

()

Details

(Whiteboard: [projectbranch])

Attachments

(6 files, 2 obsolete files)

Hi, Spoke to Damon and a few others about creating a UX project branch, so we can land experimental UI features that need testing and tweaking over time on a dedicated branch. This will be especially useful under the new release process as we can do experiments over time, and push these to mozilla-central when they are ready.
Assignee: server-ops → nobody
Component: Server Operations → Release Engineering
QA Contact: mrz → release
Project name: hg.mozilla.org/projects/ux For builds: All platforms or subset of platforms currently building mozilla-central? All desktop OSes with opt (no debug) for now. No mobile yet. Will you use the mozilla-central mozconfigs or will you need custom ones? Standard Nightly builds? Yes, we'd like to have nightly updates too, ok to get this later Need unittests? All platforms or subset of platforms currently testing mozilla-central? Yes Mobile Builds? All platforms or subset of platforms currently building mobile-browser? No Need Talos? All talos suites or a subset of suites run on mozilla-central? Yes. Name of the contact person for this branch who will: Be doing periodic refreshes from parent: fyan Be contact person for misc setup questions: limi Decide when to land back project branch onto parent: limi Decide when to terminate the project branch: limi Timeline: When should this branch go live? Whenever you can get it ready Approx expected life span of project branch? Forever
Group: infra
Priority: -- → P3
Whiteboard: [projectbranch]
Any news on this? We're ready with several UI experiments that we'd like to put on a UX branch.
Not sure how this got put to p3 - minor, but that must have kept it out of our triage queue. I'll start setting this up.
Assignee: nobody → lsblakk
Severity: minor → normal
Status: NEW → ASSIGNED
Priority: P3 → P2
Summary: Create UX project branch → New project branch request: ux
Attached patch Add Ux tinderbox/branch to tbpl (obsolete) — Splinter Review
Attachment #528729 - Flags: review?(ehsan)
Depends on: 653284
Attachment #528729 - Flags: review?(ehsan) → review+
Thanks! Two questions: 1) What do we do next to put stuff here? 2) Is it hard/time-consuming for it to be "UX" or "ux" instead of "Ux"? (I know, but I just know it'll be mis-typed again and again if we're not consistent from the start. ;)
Severity: normal → minor
Status: ASSIGNED → NEW
Component: Release Engineering → Miscellaneous
Priority: P2 → P3
Component: Miscellaneous → Release Engineering
(In reply to comment #6) > Thanks! Two questions: > > 1) What do we do next to put stuff here? So the repo exists, but I still have to attach/review/land the patches to add this branch to the automation as well as to graphserver. Once that is live I'll let you know to go ahead and push to the new repo and it should be fairly turn-key. > > 2) Is it hard/time-consuming for it to be "UX" or "ux" instead of "Ux"? (I > know, but I just know it'll be mis-typed again and again if we're not > consistent from the start. ;) Short answer: yes it's a PITA for a branch to not match the repo_name.title() - ("ux" == "Ux") in the configs. All the other new project branches use this and it allows for some great generic loops. I realize it's odd looking since your particular branch is so short but I guess I hope that it's something you all can live with.
(In reply to comment #7) > So the repo exists, but I still have to attach/review/land the patches to add > this branch to the automation as well as to graphserver. Once that is live > I'll let you know to go ahead and push to the new repo and it should be fairly > turn-key. Thanks! > > 2) Is it hard/time-consuming for it to be "UX" or "ux" instead of "Ux"? (I > > know, but I just know it'll be mis-typed again and again if we're not > > consistent from the start. ;) > > Short answer: yes it's a PITA for a branch to not match the repo_name.title() - > ("ux" == "Ux") in the configs. All the other new project branches use this and > it allows for some great generic loops. I realize it's odd looking since your > particular branch is so short but I guess I hope that it's something you all > can live with. So can't both be "UX" or "ux"? I want them to match too, just not be mixed case.
just going to run this in staging once the graphserver entries are in to make sure I got all the "UX" stuff right.
Attachment #529589 - Flags: review?(catlee)
Depends on: 654315
> So can't both be "UX" or "ux"? I want them to match too, just not be mixed > case. I'm going to try and do this as "UX" in the visible places. The repo will be 'ux'
we're using a differently named tree instead.
Attachment #528729 - Attachment is obsolete: true
Attachment #529595 - Flags: review?(ehsan)
Attachment #529595 - Flags: review?(ehsan) → review+
Comment on attachment 529589 [details] [diff] [review] data.sql patch for UX branch I'm guessing the machine names are derived from the repo name, and not the tree name?
Attachment #529589 - Flags: review?(catlee) → review+
Comment on attachment 529595 [details] [diff] [review] Add UX (no longer called 'Ux') tinderbox/branch to tbpl http://hg.mozilla.org/users/mstange_themasta.com/tinderboxpushlog/rev/a53d502076c3 landed and deployed on tbpl
Attachment #529595 - Flags: checked-in+
Attachment #529587 - Flags: review?(catlee)
(In reply to comment #11) > I'm going to try and do this as "UX" in the visible places. The repo will be > 'ux' Thank you! Sorry to be a pain. Just know that this would confuse people later. :)
I just pushed a test commit, and it worked! \o/ However, I did get the following output: remote: Not trusting file /repo/hg/mozilla/projects/ux/.hg/hgrc from untrusted user root, group scm_level_2 remote: Not trusting file /repo/hg/mozilla/projects/ux/.hg/hgrc from untrusted user root, group scm_level_2 searching for changes remote: adding changesets [...] remote: Inserted into the pushlog db successfully. remote: warning: changegroup.z_purgeurl hook exited with status 1 I don't get that "not trusting" message when pushing to or pulling from other repos. Does that file need a chmod or something? Also, the "warning: changegroup.z_purgeurl hook exited with status 1" is cryptic. Any idea what that means or whether I should be worried about it? Thanks!
Please reopen bug 653284 for both of those. The latter is to do with caching on http://hg.mozilla.org.
The changegroup.z_purgeurl warning is fixed - it was unrelated to your repo. Please chase the ownership issue though.
Attachment #529587 - Flags: review?(catlee) → review+
test push to this branch was successful in triggering builds & those are going to the right Tinderbox and TBPL. What's left to do here is add mozconfigs for this branch with the nightly update channel set to 'nightly-ux' so that updates on this branch can stay on track, also need to add to self-serve.
We'd also have to update http://mxr.mozilla.org/mozilla/source/webtools/aus/xml/inc/config-dist.php#120 to add nightly-ux. I have something else to push out in that file today so we could do that at the same time.
Comment on attachment 531700 [details] [diff] [review] config-dist.php patch for enabling nightly-ux update channel Need to update http://mxr.mozilla.org/mozilla/source/webtools/aus/xml/inc/config-dist.php#120 too, should have mentioned that in my earlier comment.
Attachment #531700 - Flags: review?(nrthomas) → review-
now with the additional mapping to the aus upload dir (which I confirmed will match what gets passed in by configs - the generic project branch loop uses branch name)
Attachment #531700 - Attachment is obsolete: true
Attachment #531789 - Flags: review?(nrthomas)
Attachment #531706 - Flags: review?(nrthomas) → review+
Comment on attachment 531789 [details] [diff] [review] config-dist.php patch for enabling nightly-ux update channel (take 2) Review of attachment 531789 [details] [diff] [review]: -----------------------------------------------------------------
Attachment #531789 - Flags: review?(nrthomas) → review+
So once the AUS configs are landed and deployed I can push & land the mozconfig/buildbot-config changes that will turn on the nightly updates for this branch. Hopefully the AUS work can happen tomorrow, Catlee or Nthomas can land the AUS patch and IT can deploy.
Comment on attachment 531789 [details] [diff] [review] config-dist.php patch for enabling nightly-ux update channel (take 2) [catlee] aus/xml/inc:1% cvs commit config-dist.php Checking in config-dist.php; /cvsroot/mozilla/webtools/aus/xml/inc/config-dist.php,v <-- config-dist.php new revision: 1.143; previous revision: 1.142 done [catlee] aus/xml/inc% cvs tag -F AUS2_PRODUCTION config-dist.php T config-dist.php
Attachment #531789 - Flags: checked-in+
Depends on: 657008
Comment on attachment 531706 [details] [diff] [review] adds mozconfigs and ux branch snippet generation for nightlies http://hg.mozilla.org/build/buildbot-configs/rev/00de559dc62a landed on default
Attachment #531706 - Flags: checked-in+
End of the week status update: The AUS change has landed, bug 657008 will update the live snippet server so that once the configs in https://bugzilla.mozilla.org/attachment.cgi?id=531706 are put live into production all the wiring will be in place for updates between UX branch nightlies. Releng usually does reconfigs of our automation masters on Tuesday and Thursday so optimistic guess is that this should be in effect for next Wednesday's nightlies.
(In reply to comment #31) > all the wiring will be in place for updates between UX branch > nightlies. Releng usually does reconfigs of our automation masters on > Tuesday and Thursday so optimistic guess is that this should be in effect > for next Wednesday's nightlies. Thank you!
(In reply to comment #30) > Comment on attachment 531706 [details] [diff] [review] [review] > adds mozconfigs and ux branch snippet generation for nightlies > > http://hg.mozilla.org/build/buildbot-configs/rev/00de559dc62a landed on > default Merged in production and reconfigured masters.
The nightly that is generated tonight should be set to the right channel, we can force a second nightly tomorrow to test updating is properly set up.
(In reply to comment #35) > Created attachment 534039 [details] > attempt at readme for the latest-ux directory Added to the latest-ux dir: http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/latest-ux/README.txt This branch is now running smoothly, so I'm closing the bug. Re-open if anything comes up.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
I'm reopening this bug because I haven't been receiving nightly updates on OSX.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Margaret, could you grab the AUS query URL for your build ? That's in the Error Console after toggling app.update.log to true in about:config, and opening the Error Console and the About dialog.
(In reply to comment #38) > Margaret, could you grab the AUS query URL for your build ? That's in the > Error Console after toggling app.update.log to true in about:config, and > opening the Error Console and the About dialog. AUS:SVC Checker:getUpdateURL - update URL: https://aus3.mozilla.org/update/3/Firefox/7.0a1/20110603040211/Darwin_x86_64-gcc3-u-i386-x86_64/en-US/nightly-ux/Darwin%2010.7.0/default/default/update.xml?force=1
Fixed now for ux and jaegermonkey. It was a Mac specific issue caused by publishing snippets to a Darwin_x86_64-gcc3 directory, and the clients querying using different build targets. # ffxbld@aus2-staging $ cd /opt/aus2/incoming/2/Firefox/ux $ ln -s Darwin_x86_64-gcc3 Darwin_x86_64-gcc3-u-i386-x86_64 $ ln -s Darwin_x86_64-gcc3 Darwin_x86-gcc3-u-i386-x86_64 I've added a template directory with those symlinks. Next time we add a branch with nightly updates enabled do # ffxbld@aus2-staging $ rsync -av ~/template/ /opt/aus2/incoming/2/Firefox/<new_branch_name>/
Status: REOPENED → RESOLVED
Closed: 14 years ago14 years ago
Resolution: --- → FIXED
Thanks nthomas! I put that info in here https://wiki.mozilla.org/ReleaseEngineering:ProjectBranchPlanning#Release_Engineering_Project_Branch_Creation_Checklist to help the set up of future project branch nightly updates.
Status: RESOLVED → VERIFIED
Blocks: 697289
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: