Closed Bug 608114 Opened 14 years ago Closed 14 years ago

Adapt to symbols upload changes for post-upload command in bug 607951 and friends


(Camino Graveyard :: General, defect)

Not set


(Not tracked)



(Reporter: alqahira, Assigned: alqahira)



(Whiteboard: [camino-2.0.6])


(3 files, 2 obsolete files)

Per bug 607951, it looks like we'll need to make only 2 changes (on all active branches):

1) 'export'ing the symbols index filename in our Makefile (so it's available to the environment and scripts)

2) setting the 'POST_SYMBOL_UPLOAD_CMD' env variable in all of our tinderconfigs.  We'll need to know the final path to the command that we should use.

In addition,

3) We'll need to ensure that the relevant changes to toolkit's land on 1.9.0 for Camino 2.0.x builds ;)

4) We'll probably want to port changes to the final upload command into the re-upload script generation:
Depends on: 607951
Attached patch Makefile changesSplinter Review
This should do 1 and 4, the Makefile bits.
Attachment #487518 - Flags: superreview?(stuart.morgan+bugzilla)
And for the tinderconfigs, the path-value for the new env variable appears to be '/usr/local/bin/'

I'll upload the tinderconfig diffs (for sanity) later.
Attached patch 1.9.2 tinder-configs (obsolete) — Splinter Review
Stuart, just looking for a sanity-check from you on these two patches; we really only care about cb-x1 (the one with no machine-name in the path) and cb-x4, but I've modified the other configs that had symbols info to keep them updated.
Attachment #488115 - Flags: superreview?(stuart.morgan+bugzilla)
Attached patch CAMINO_2_0_BRANCH tinder-configs (obsolete) — Splinter Review
Attachment #488116 - Flags: superreview?(stuart.morgan+bugzilla)
Comment on attachment 488116 [details] [diff] [review]
CAMINO_2_0_BRANCH tinder-configs

(I've also made this change to the on-machine Cm2.0.5 tinder-config, so that when it gets copied and edited for 2.0.6, it will pick up this change without me forgetting.)
Comment on attachment 487518 [details] [diff] [review]
Makefile changes

Attachment #487518 - Flags: superreview?(stuart.morgan+bugzilla) → superreview+
Comment on attachment 488115 [details] [diff] [review]
1.9.2 tinder-configs

Attachment #488115 - Flags: superreview?(stuart.morgan+bugzilla) → superreview+
Attachment #488116 - Flags: superreview?(stuart.morgan+bugzilla) → superreview+
Holding off on landing the tinder-configs until there's movement on bug 607951 and/or bug 607946 and/or branch movement on bug 607946.

I don't want to get us into a situation where has been updated on the branches to use the command but the command (or its no-op version) hasn't been installed on the symbols upload server and causes errors when doing symbol upload, which would be a situation where the otherwise no-op tinder-config changes became op.
Whiteboard: [camino-2.0.6]
Now with less build failures due to missing ;s
Attachment #488115 - Attachment is obsolete: true
Now with less build failures due to missing ;s
Attachment #488116 - Attachment is obsolete: true
Bug 607946 is in on branches, and bug 609270 is also live (the no-op version), so I landed the tinder-config changes on both branches.

That means we're all ready whenever bug 607951 and bug 607961 happen to land.  It doesn't look like it'll happen while I'm gone, but I'll've definitely forgotten about this by the time I'm back.

We'll need to check tomorrow's nightlies' symbol uploads to make sure they went OK, though.
Closed: 14 years ago
Resolution: --- → FIXED
(And I've updated my OS Symbols convenience scripts to fetch and export the symbol index filename and the post-upload command path, too:  As long as we keep cb-x1's 2.1 tinderconfig updated, I'll pull the right thing [and we can change it to cb-x4 if we need to, but x1 has a shorter path :P ])
You need to log in before you can comment on or make changes to this bug.