Closed
Bug 1422069
Opened 8 years ago
Closed 8 years ago
add BBB updates builder for in-tree relpro
Categories
(Release Engineering :: Release Automation, enhancement)
Release Engineering
Release Automation
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: mtabara, Assigned: bhearsum)
References
Details
Attachments
(1 file)
|
11.57 KB,
patch
|
mozilla
:
feedback+
|
Details | Diff | Splinter Review |
Once we have the release balrog stuff in-tree, we can proceed with adjusting the balrogscript code to also handle the "updates builder" logic within in.
That means publishing top-level release information.
We already have those calls from the updates builder so I only need to find the proper way to integrate that within the existing balrogworkers.
| Assignee | ||
Comment 1•8 years ago
|
||
Mihai, while you were out today I realized that we not only need to do this, but _also_ update the patcher and update verify configs. In the interest of expediency, I put together a patch that will simply start running the buildbot "updates" builder for now. We'll need to get rid of this as part of the no-bbb project, but I _think_ we can live with this in the short term.
This patch should start firing the updates builder correctly for all branches - including setting "channels" and "generate_bz2_blobs" correctly for RCs. I also added it as a dependency for the approptiate update/final verify builder, which _should_ make them work. The updates builder itself has no dependencies of its own - everything it needs to function is derived from ship-it/release configs.
I needed to add appVersion to the release config for this, which ended up in a few other places too. It's not doing any harm, but it's a PITA to only add it for this task. I can push harder on that if it's important.
Attachment #8933787 -
Flags: feedback?(aki)
Updated•8 years ago
|
Attachment #8933787 -
Flags: feedback?(aki) → feedback+
| Reporter | ||
Comment 2•8 years ago
|
||
Re-assigning to :bhearsum since he's doing the heavy lifting here.
Assignee: mtabara → bhearsum
| Assignee | ||
Comment 3•8 years ago
|
||
(In reply to Mihai Tabara [:mtabara]⌚️GMT from comment #2)
> Re-assigning to :bhearsum since he's doing the heavy lifting here.
Just for the record, I'm only taking care of running the existing updates builder as part of in-tree release promotion. When we start tackling no-bbb stuff, we need to do more (which may be done by me, or someone else).
| Reporter | ||
Comment 4•8 years ago
|
||
(In reply to Ben Hearsum (:bhearsum) from comment #3)
> (In reply to Mihai Tabara [:mtabara]⌚️GMT from comment #2)
> > Re-assigning to :bhearsum since he's doing the heavy lifting here.
>
> Just for the record, I'm only taking care of running the existing updates
> builder as part of in-tree release promotion. When we start tackling no-bbb
> stuff, we need to do more (which may be done by me, or someone else).
You're right, title is confusing, let's change it to what the bug is related to.
Threre's a trello card that tracks the balrogscript updates builder anyway.
Summary: adjust balrogscript release behavior to publish top-level information too (a.k.a integrate updates builder within balrogworkers) → add BBB updates builder for in-tree relpro
| Assignee | ||
Updated•8 years ago
|
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•