Closed Bug 927671 Opened 11 years ago Closed 10 years ago

Deploy mozmake on windows build slaves

Categories

(Infrastructure & Operations :: RelOps: General, task, P3)

x86_64
Windows Server 2008

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: glandium, Assigned: markco)

References

Details

Attachments

(1 file)

260.00 KB, application/x-msdos-program
Details
      No description provided.
Blocks: 927672
Found in triage.

(aside: would this change need to "ride the trains", to avoid any risk of binary compat issues?)
Component: Other → Platform Support
QA Contact: joduinn → coop
It depends what current version of mozillabuild is deployed, and what the new version will contain that is different. If the current version is deployed and Ryan only adds mozmake, then it won't affect anything, since it's only adding a binary. Ryan may want to also update hg, which should be safe, too.
If an older mozillabuild is deployed, then i don't know.
Alternatively, it is also possible to only deploy mozmake.exe, if that's deemed less risky than updating an old mozillabuild or updating mercurial.
Depends on: 928594
No longer depends on: 927213
Armen, do you know what version of MozillaBuild is currently deployed on our various build machines? (Incl release branches) :-)
Flags: needinfo?(armenzg)
Can we please install only mozmake.exe?
It seems that it is not part of the current installation and it makes it for us a NPOTB.

However, any of the other parts that could come from Mozilla-Build from 1.5.1 to 1.9 could cause a regression to the release process while a release is happening.
Unfortunately, grabbing new changes, adding it to a handful machine and re-verify our whole release process is rather involved.

Would this work for you?

cltbld@W64-IX-SLAVE43 /c/mozilla-build
$ cat VERSION
1.5.1

cltbld@W64-IX-SLAVE43 /c/mozilla-build
$ hg/hg.exe --version
Mercurial Distributed SCM (version 1.9.1)
(see http://mercurial.selenic.com for more information)

Copyright (C) 2005-2011 Matt Mackall and others
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
Flags: needinfo?(armenzg)
OS: Linux → Windows Server 2008
Oh my, I was assuming we were using a more recent mozilla-build.

Then I'd rather wait for bug 944649.
Depends on: 944649
No longer depends on: 928594
Yeah :/

Please poke me once we're ready and we'll see who can grab it.
Assignee: nobody → coop
Priority: -- → P3
glandium: are we still waiting on bug 927671? Any progress there?
(In reply to Chris Cooper [:coop] from comment #8)
> glandium: are we still waiting on bug 927671? Any progress there?

Yes, I'm just waiting for upstream.
Assignee: coop → relops
Component: Platform Support → RelOps
Product: Release Engineering → Infrastructure & Operations
QA Contact: coop → arich
Summary: Deploy new version of MozillaBuild from bug 927213 on windows build slaves → Deploy mozmake on windows build slaves
Version: unspecified → other
Attached file mozmake.exe
Please deploy this version. It is the one we'll have in MozillaBuild 1.9 final.
(In reply to Mike Hommey [:glandium] from comment #10)
> Please deploy this version. It is the one we'll have in MozillaBuild 1.9
> final.

Which I'm planning to release by the end of the week.
Blocks: 920198
Assignee: relops → mcornmesser
In the end, we're going to use tooltool to deploy mozmake.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → WONTFIX
Blocks: 990739
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: