SeaMonkey needs access to DXSDK_Feb10.exe and newest hg updates

RESOLVED FIXED

Status

Release Engineering
General
P2
normal
RESOLVED FIXED
7 years ago
5 years ago

People

(Reporter: Callek, Assigned: nthomas)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

7 years ago
SeaMonkey is looking to do an update on our windows builders, and to do so we need access to (many) of the OPSI files that are used by Firefox.

We do not yet have OPSI running, but we will be manually installing many of the OPSI updates that Firefox Builders now have. One of our main ones, that we feel is heavily needed is the DXSDK install, and as such we need at the least the DXSDK_Feb10.exe accessible to our builders somehow.

This was solved for the puppet-files by creating a mount on stage, /mnt/puppet-files/{production,staging} which we are able to use there.

We plan to release SeaMonkey 2.1 based on Firefox 4.0.1, and would even like the DirectX part fixed for b3 if possible, so this is relatively important to us.
Two notes:
I would recommend against running OPSI, as we are working towards dropping it. It's more pain than it's worth.

We can't share the entirety of our OPSI files because it would leak secrets, like has happened with the puppet files (bug 635638).
(Reporter)

Comment 2

7 years ago
(In reply to comment #1)
> Two notes:
> I would recommend against running OPSI, as we are working towards dropping it.
> It's more pain than it's worth.

Fair enough, I won't plan to get OPSI up and running on our end.

> We can't share the entirety of our OPSI files because it would leak secrets,
> like has happened with the puppet files (bug 635638).

That is fair enough as well (I can't access 635638 to know what the specific issue was, but if thats indicating that /mnt/puppet-files/ is going away, I'd like to have a further discussion with you guys and maybe IT, separate from this).

In the short term, what I need is the DXSDK file as outlined here, I am happy to file specific bugs with getting necessary other files as I need them, the largest issue is how to get them from <x> to SeaMonkey build machines though. So I would be happy if its somewhere I can hg/cvs/svn/etc. pull from (using the seabld user) or if its a place to scp from, etc. I just don't know what works for you guys.
(Reporter)

Comment 3

7 years ago
I wonder if we can get some traction here, and or a short-term plan that can work.

CC-ing jduin so we can figure this out.
(Reporter)

Comment 4

7 years ago
Per IRC: Jduin is ok with this provided we are _sure_ the files are not leaking secrets/security.

Also per IRC: Nthomas suggested just dumping the wanted files to seabld's user directory.

I am also asking for the hg update files while I'm at it, as I suspect that trying to enable hg shared on our slaves will help our build times immensely.
Summary: SeaMonkey needs access to OPSI Files (specifically DXSDK_Feb10.exe) → SeaMonkey needs access to DXSDK_Feb10.exe and newest hg updates
(Assignee)

Updated

7 years ago
Assignee: nobody → nrthomas
Priority: -- → P2
(Assignee)

Comment 5

7 years ago
Referencing the bugs where the upgrades happen would've been helpful. I'm assuming you mean bug 529938, and mercurial v1.7.5 from bug 589885.
(Assignee)

Comment 6

7 years ago
Copied to seabld@stage:~/packages/
Status: NEW → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → FIXED
(Reporter)

Updated

7 years ago
Blocks: 642723
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.