expose relbranch on release kickoff form

RESOLVED FIXED

Status

Release Engineering
Release Automation
RESOLVED FIXED
5 years ago
5 years ago

People

(Reporter: bhearsum, Assigned: bhearsum)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [shipit])

Comment hidden (empty)
(Assignee)

Updated

5 years ago
Duplicate of this bug: 811847
(Assignee)

Updated

5 years ago
Whiteboard: [kickoff]
(Assignee)

Comment 2

5 years ago
This is easy! Need to update a few things:
* The model: https://github.com/bhearsum/release-kickoff/blob/master/kickoff/model.py#L5
* The form: https://github.com/bhearsum/release-kickoff/blob/master/kickoff/views/submit.py#L13
* The templates: https://github.com/bhearsum/release-kickoff/blob/master/kickoff/templates/releases.html and https://github.com/bhearsum/release-kickoff/blob/master/kickoff/templates/submit_release.html
* The release config templates (all the .template files in https://github.com/mozilla/build-buildbot-configs/tree/master/mozilla)

And I'm pretty sure release runner will pass along relbranch without any modifications to it.

relbranch should be an optional parameter, and default to "None". NEed to make sure that gets substituted correctly in the release configs as None (rather than "None").
Priority: -- → P3
(Assignee)

Comment 3

5 years ago
Not having this caused huge problems with releases today. We need to fix this soon.
Priority: P3 → --
(Assignee)

Comment 4

5 years ago
Going to do this soon.
Assignee: nobody → bhearsum
(Assignee)

Comment 5

5 years ago
Fixed this at the same time as bug 823841. Did them both in one set of patches for simplicity.
Status: NEW → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → FIXED
(Assignee)

Updated

5 years ago
Whiteboard: [kickoff] → [shipit]
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.