Closed Bug 650449 Opened 14 years ago Closed 14 years ago

need a mozilla-2.1 debsign builder on pmm

Categories

(Release Engineering :: General, defect, P1)

x86
macOS
defect

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: lsblakk, Assigned: lsblakk)

References

Details

Attachments

(2 files, 2 obsolete files)

No description provided.
so i'm not sure about the locales files - do i need to add that somewhere?
Attachment #526766 - Flags: feedback?(aki)
will run this in staging, just looking to see what i might be missing
Attachment #526768 - Flags: feedback?(aki)
Comment on attachment 526766 [details] [diff] [review] add mozilla-2.1 to mozharness deb_repos >--- a/configs/deb_repos/trunk_nightly.json >+++ b/configs/deb_repos/mozilla-2.1_nightly.json >@@ -1,42 +1,42 @@ > { > "log_name": "signdebs", >- "locales_file": "mozilla-central/mobile/locales/all-locales", >+ "locales_file": "mozilla-2.1/mobile/locales/all-locales", > "hg_repos": [{ >- "repo": "http://hg.mozilla.org/mozilla-central", >- "dir_name": "mozilla-central" >+ "repo": "http://hg.mozilla.org/releases/mozilla-2.1", >+ "dir_name": "mozilla-2.1" > }], There is no mozilla-2.1/mobile directory. We probably want "locales_file": "mobile-2.0/locales/all-locales", "hg_repos": [{ "repo": "http://hg.mozilla.org/releases/mobile-2.0", "dir_name": "mobile-2.0" }], specifically because this is a pre-mobile-merge hg repository. Same in the staging file. http://hg.mozilla.org/releases/mobile-2.0/file/default/locales/all-locales Other than that pre-merge complication, this looks good :)
Attachment #526766 - Flags: feedback?(aki) → feedback-
Comment on attachment 526768 [details] [diff] [review] buildbot configs for mozilla-2.1 debsign >--- a/debsign/config-production.py >+++ b/debsign/config-production.py >@@ -1,14 +1,23 @@ > SLAVES = { > "linux": ["debsign1"], > } > > BRANCHES = { > "mozilla-central": {}, >+ "mozilla-2.1": {}, > } > BRANCHES["mozilla-central"]["script_repo_tag"] = 'default' > BRANCHES["mozilla-central"]["nightly_config_file"] = "deb_repos/trunk_nightly.json" > BRANCHES["mozilla-central"]["nightly_platforms"] = ["fremantle", "fremantle-qt"] > BRANCHES["mozilla-central"]["enable_release"] = True > BRANCHES["mozilla-central"]["release_config_file"] = "deb_repos/4.0_release.json" > BRANCHES["mozilla-central"]["release_platforms"] = ["fremantle"] > BRANCHES["mozilla-central"]["nightly_hour"] = 4 Let's set enable_release to False and remove the release_config_file and release_platforms lines. Not required, but it'll be cleaner. We actually had a builder for the 4.0.1 release; it was just named the wrong thing, and caused confusion. Same for staging.
Attachment #526768 - Flags: feedback?(aki) → feedback+
Attachment #526766 - Attachment is obsolete: true
Attachment #527053 - Flags: review?(aki)
Attachment #526768 - Attachment is obsolete: true
Attachment #527054 - Flags: review?(aki)
Attachment #527053 - Flags: review?(aki) → review+
Attachment #527054 - Flags: review?(aki) → review+
Attachment #527053 - Flags: checked-in+
got my 4.0.1 repos!
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: