update TBPL for mozilla-b2g18 branch

RESOLVED FIXED

Status

Tree Management Graveyard
TBPL
RESOLVED FIXED
5 years ago
3 years ago

People

(Reporter: hwine, Assigned: hwine)

Tracking

Dependency tree / graph

Details

(Whiteboard: [re-b2g])

Attachments

(1 attachment)

(Assignee)

Description

5 years ago
Created attachment 686854 [details] [diff] [review]
add the mapping

Branch coming soon, test builds soon after.
Attachment #686854 - Flags: review?(edmorley.bugzilla)
Comment on attachment 686854 [details] [diff] [review]
add the mapping

lgtm :-)
Attachment #686854 - Flags: review?(edmorley.bugzilla) → review+
Assignee: nobody → hwine
Status: NEW → ASSIGNED
Component: Release Engineering: Automation (General) → Tinderboxpushlog
Product: mozilla.org → Webtools
QA Contact: catlee
Version: other → Trunk
(Assignee)

Comment 2

5 years ago
Comment on attachment 686854 [details] [diff] [review]
add the mapping

thx - huh - no committed flag over here.

Committed: http://hg.mozilla.org/users/mstange_themasta.com/tinderboxpushlog/rev/0422b04bb0d4
(Assignee)

Comment 3

5 years ago
Ed - I'm new to this, so a bit confused about the product/assignment changes for this bug.

Last time we did this (esr17 - bug 808017), you opened a 2nd bug for deployment (bug 809543).

Please let me know what the next step is - if it's just that rail & I filed in the wrong place, I'll update our docs.

Thanks!
(In reply to Hal Wine [:hwine] from comment #3)
> Ed - I'm new to this, so a bit confused about the product/assignment changes
> for this bug.

Ah bug 808017 was in the wrong component, I've just moved that too :-)

TBPL bugs live in Webtools:Tinderboxpushlog, the pushes to production need to be performed by IT (since I do not have access), so I file another bug - typically in mozilla.org::Server Operations - Web operations. My only request if you file one yourself is to CC :edmorley & tinderboxpushlog@webtools.bugs since I don't watch mozilla.org components. Example previous production push is bug 815738.

In what timeframe do you need this in production? Only reason I ask is that nthomas had to request a push only yesterday & I try to avoid risking pestering IT with too many requests close together if possible (in the hope that it means when I do need a rush-push, they won't mind so much). I also have a couple of things of my own that will hopefully be landing by Monday. 

Before the push to production this can be tested on tbpl-dev (https://tbpl-dev.allizom.org/ , credentials at https://intranet.mozilla.org/Websites/Stage_Passwords#TBPL), or by running index.html from the local filesystem (automatically uses the backend on production - the local UI will understand the new tree).

Let me know if you would like an urgent push to prod or if this can wait until first half of next week & I can file the bugs either way :-)
Sorry just spotted "B2g18".

Would you mind s/B2g18/B2G18/ ? :-)
(Assignee)

Comment 6

5 years ago
(In reply to Ed Morley [UTC+0; email:edmorley@moco] from comment #5)
> Sorry just spotted "B2g18".
> 
> Would you mind s/B2g18/B2G18/ ? :-)

No issue on my end - I haven't opened the requests yet for the associated database updates. I was just following the "pattern" from Esr17. Having all caps does make it harder to spot the number (there will be other such branches in the future).

Go ahead and change it - let me know if you do though.
Fair point; I'll leave as is :-)
(Assignee)

Comment 8

5 years ago
bah - had this sitting unsaved in a tab - I think we're already on this course

(In reply to Ed Morley [UTC+0; email:edmorley@moco] from comment #4)
> In what timeframe do you need this in production? ...
> ... I also
> have a couple of things of my own that will hopefully be landing by Monday. 

That should be fine - worst case if they call for an early deploy, we
can rush it then.

> Before the push to production this can be tested on tbpl-dev
> (https://tbpl-dev.allizom.org/ , credentials at
> https://intranet.mozilla.org/Websites/Stage_Passwords#TBPL), or by running
> index.html from the local filesystem (automatically uses the backend on
> production - the local UI will understand the new tree).

Awesome - I'm adding that to our docs. Thanks!
(In reply to Hal Wine [:hwine] from comment #8)
> Awesome - I'm adding that to our docs. Thanks!

Where are these docs out of curiosity? :-)
Depends on: 817713
In production :-)
Status: ASSIGNED → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → FIXED
Product: Webtools → Tree Management
Product: Tree Management → Tree Management Graveyard
You need to log in before you can comment on or make changes to this bug.