Closed Bug 1114876 Opened 9 years ago Closed 6 years ago

[Tracking Bug] Get initial SeaMonkey Windows 2008 configured.

Categories

(SeaMonkey :: Release Engineering, defect)

x86_64
Windows 8.1
defect
Not set
blocker

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: ewong, Assigned: Callek)

References

Details

Currently, our Windows slaves  are based on Windows 2003 which is
'old'; but more to the point that trunk is now no longer buildable
on these systems due to the VS2013 requirement.

We need to have our Windows slaves migrated/configured to Windows 2008.
This bug tracks this progress.
Assignee: nobody → bugspam.Callek
Depends on: 1116887
It has been exactly 6 months since this bug report was filed and there seems to be no significant progress on this.

Microsoft will end support for Windows Server 2003 next month on Tuesday July 14, 2015 as noted here:
http://www.microsoft.com/en-us/server-cloud/products/windows-server-2003/
Time is running out on Windows 2003 as Microsoft will no longer offer any more new updates after 7/14/2015.

So how SOON will those SM Windows machines be upgraded to Windows Server 2008 R2, Edmund?
Lack of continuing support for Windows Server 2003 is of negligible consideration here; as you may or may not have noticed, both SeaMonkey nightly test but also release builds have been broken on Windows since the 2.33 cycle (hence that's the current and last available release). Having said that, ewong doesn't seem to have any influence on the building machine themselves, which are provided and ultimately maintained by Mozilla server ops. Thus, it's on their turf to perform the actual updates of the SeaMonkey builders according to their own specs as enforced with the Gecko 37.0 cycle.
(In reply to erpman1 from comment #1)
> It has been exactly 6 months since this bug report was filed and there seems
> to be no significant progress on this.
> 
> Microsoft will end support for Windows Server 2003 next month on Tuesday
> July 14, 2015 as noted here:
> http://www.microsoft.com/en-us/server-cloud/products/windows-server-2003/
> Time is running out on Windows 2003 as Microsoft will no longer offer any
> more new updates after 7/14/2015.
> 
> So how SOON will those SM Windows machines be upgraded to Windows Server
> 2008 R2, Edmund?

As mentioned by rsx11m, I am not the one doing the upgrade (since I have
no access to those machines aside for SSH and you can't upgrade a system
via SSH, afaik) nor am I coordinating the effort of doing that task.  Callek's
the person coordinating this effort.

So I'm afraid I don't have the ETA.  

What I am trying to do is to generate official builds on a loaner, so hopefully
people will still have that as a backup; but right now, it's a bit slow
as figuring out how to do a build (say, nightly) given the buildbot steps
is proving to be a little harder than I thought.




I don't have physical access to the Windows servers
so I am not the one doing the upgrading and ergo, I don't know the ETA.
Iiuc, this is now a blocker.
Severity: normal → blocker
Version: unspecified → Trunk
Workaround for L64, W32, W64 and langpacks:
https://l10n.mozilla-community.org/~akalla/unofficial/seamonkey/nightly/
then browse down to the desired branch and architecture.

As the URL indicates, these are unofficial. AFAIK they are built from original Mozilla sources but not on Mozilla machines.

Disclaimer: I cannot test the Windows builds, I'm on Linux; but it seems that Linux SeaMonkey is also not building at Mozilla at the moment. I found today's nightly at the above URL (subdirectory latest-comm-central-linux64) and I'm using it at the moment.
Blocks: 482143
Closing this as wf.  SCL3 is gone.  We aren't in MD-1 (or whatever it's called)..  and
we have our own infra.
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.