Closed Bug 812322 Opened 12 years ago Closed 11 years ago

expose relbranch on release kickoff form

Categories

(Release Engineering :: Release Automation: Other, defect)

Product:
Release Engineering
Component:
Release Automation: Other
Platform:
x86_64
Linux
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: bhearsum, Assigned: bhearsum)

References

Details

(Whiteboard: [shipit]) 

      No description provided.
Whiteboard: [kickoff]
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
Not having this caused huge problems with releases today. We need to fix this soon.
Priority: P3 → --
Going to do this soon.
Assignee: nobody → bhearsum
Fixed this at the same time as bug 823841. Did them both in one set of patches for simplicity.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Whiteboard: [kickoff] → [shipit]
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.