Closed
Bug 915596
Opened 11 years ago
Closed 11 years ago
Set up gaia pushbot for B2G 1.2
Categories
(Developer Services :: Mercurial: hg.mozilla.org, defect)
Developer Services
Mercurial: hg.mozilla.org
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: catlee, Assigned: mozilla)
References
Details
Attachments
(2 files, 1 obsolete file)
2.25 KB,
patch
|
hwine
:
review+
|
Details | Diff | Splinter Review |
989 bytes,
patch
|
hwine
:
review+
|
Details | Diff | Splinter Review |
We need to set up the gaia pushbot to track the (yet to be created) v1.2 branch in gaia and update gaia.json on mozilla-aurora.
Assignee | ||
Updated•11 years ago
|
Assignee: nobody → aki
Assignee | ||
Comment 1•11 years ago
|
||
Assignee | ||
Comment 2•11 years ago
|
||
With testing configs, which I'm going to run now from my laptop for sanity.
Attachment #805715 -
Attachment is obsolete: true
Assignee | ||
Comment 3•11 years ago
|
||
Comment on attachment 805720 [details] [diff] [review] gaia-pushbot The push to my user repo mozilla-aurora died... my theory is that the massive push log for the first sync killed hg's commit. The good thing is, the existing gaia.json should be good until the first push to the gaia-1_2 branch.
Attachment #805720 -
Flags: review?(hwine)
Comment 4•11 years ago
|
||
Comment on attachment 805720 [details] [diff] [review] gaia-pushbot Review of attachment 805720 [details] [diff] [review]: ----------------------------------------------------------------- lgtm - everything lines up.
Attachment #805720 -
Flags: review?(hwine) → review+
Assignee | ||
Comment 5•11 years ago
|
||
Comment on attachment 805720 [details] [diff] [review] gaia-pushbot https://hg.mozilla.org/build/mozharness/rev/4e62f84bbfac This won't go live until this merges to the production branch. Then it won't be able to make any changes until aurora is reopened. Should be live after those two things happen.
Assignee | ||
Comment 6•11 years ago
|
||
Live, though I haven't seen any changes to gaia-1_2 yet to verify. The only concern I have here is the Approval Required status which may require a tweak to the commit comment.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Assignee | ||
Comment 7•11 years ago
|
||
10:16:24 INFO - remote: ************************** ERROR **************************** 10:16:24 INFO - remote: Pushing to an APPROVAL REQUIRED tree requires your top changeset comment to include: a=... (or, more accurately, a\S*=...) 10:16:24 INFO - remote: *************************************************************
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Assignee | ||
Comment 8•11 years ago
|
||
add a=NPOTB to the commit message
Attachment #806756 -
Flags: review?(hwine)
Comment 9•11 years ago
|
||
Comment on attachment 806756 [details] [diff] [review] approval lgtm
Attachment #806756 -
Flags: review?(hwine) → review+
Assignee | ||
Comment 10•11 years ago
|
||
https://hg.mozilla.org/releases/mozilla-aurora/rev/3c6244bf7686 Yay
Status: REOPENED → RESOLVED
Closed: 11 years ago → 11 years ago
Resolution: --- → FIXED
Comment 11•11 years ago
|
||
Comment on attachment 806756 [details] [diff] [review] approval Review of attachment 806756 [details] [diff] [review]: ----------------------------------------------------------------- ::: scripts/bump_gaia_json.py @@ +107,5 @@ > changeset_config['node'][:12], > changeset_config['author'], > changeset_config['desc'], > ) > + message = 'Bumping gaia.json for %d %s revision(s) a=NPOTB\n' % ( Please can we change this? It is indeed part of the build, so something like a=gaia-sync would be more accurate... :-)
Comment 12•11 years ago
|
||
(In reply to Ed Morley [:edmorley UTC+1] from comment #11) > Please can we change this? Moved to bug 918701 :-)
Updated•10 years ago
|
Product: Release Engineering → Developer Services
You need to log in
before you can comment on or make changes to this bug.
Description
•