627414 - Project branch request: projects/build-system

Status: RESOLVED FIXED

(Release Engineering :: General, defect, P3)

Description

[(not currently active) Ted Mielczarek]

Name of hg repo for this branch (relative to hg.mozilla.com):
    projects/build

Do you want builds? Y
    All o.s.
    Incremental-build-on-checkin? Y
    Nightly builds? N

Do you want unittests? Y

Do you need mobile builds? Y
    All o.s.
    Incremental-build-on-checkin? Y

Do you want talos? N

Name of the contact person for this branch: 
    Ted Mielczarek

Timeline:
    Is this branch is needed for a specific hard calendar deadline? No
    Approx expected life span of project branch? Indefinite

Comment 1

[John O'Duinn [:joduinn] (please use "needinfo?" flag)]

ted: 

1) From https://wiki.mozilla.org/ReleaseEngineering:ProjectBranchPlanning, can you copy-paste the questions and your answers? I know it looks like a lot of questions, but this is the minimal set of questions that we hit during every branch setup. Having all this from the start really helps us avoid stop-and-redo work.

2) The name "build" is just too confusing, with all the other build related repos, so I'd like to avoid that. What exactly are you using this for? If its for MozillaBuild, would you be ok using projects/MozillaBuild instead?

Comment 2

[Benjamin Smedberg]

/me suggests build-system

Comment 3

[(not currently active) Ted Mielczarek]

Er, I did copy and paste that, is there anything I missed?

build-system is fine, I don't honestly care. We should redirect bug 627410 though.

Comment 4

[(not currently active) Ted Mielczarek]

Sorry, I guess I left out that last section, it kind of read like an "Optional" section at first:

Additional requests:

    By default project branches do not have l10n:
        No l10n necessary
    Need any changes to toolchain used in parent branch? No
    Need any changes to the compile/link/repack steps used in parent branch? No
    Do you expect to create any releases from this project branch? No
    Any other info that might be helpful to us? Not AFAIK

Comment 5

[(not currently active) Ted Mielczarek]

Sure, let's go with that.

Comment 6

[Lukas Blakk [:lsblakk] use ?needinfo]

Branch is up, I've pushed a couple times to trigger builds, let's look at them tomorrow and make sure all your project branch needs are satisfied and the wiring is good.

Comment 7

[Phil Ringnalda (:philor)]

Linux QT is looking for a mozconfig in a rather odd spot, http://hg.mozilla.org/build/buildbot-configs/file/production/mozilla2/linuxqt/generic/nightly/mozconfig rather than http://hg.mozilla.org/build/buildbot-configs/file/production/mozilla2/linux/generic/qt/mozconfig where it seems to actually be.

Comment 8

[(not currently active) Ted Mielczarek]

We don't seem to have unit tests from your pushes. Is that expected? My request did ask for unit tests.

Comment 9

[Lukas Blakk [:lsblakk] use ?needinfo]

Attachment: handling linuxqt mozconfigs

they are burning right now because of looking in nightly mozconfigs

Comment 10

[Lukas Blakk [:lsblakk] use ?needinfo]

(In reply to comment #8)
> We don't seem to have unit tests from your pushes. Is that expected? My request
> did ask for unit tests.

You are absolutely supposed to have them and I am currently investigating. I expect to have them working today.

Comment 11

[Lukas Blakk [:lsblakk] use ?needinfo]

Tests should be coming online shortly, as I am reconfiging the test-masters and they are picking up the new branch now.  Please push a new set of builds and that set should get tests running, ping me in #build if that is not the case.

Comment 12

[Lukas Blakk [:lsblakk] use ?needinfo]

Comment on attachment 513185 [details] [diff] [review]
handling linuxqt mozconfigs

landed http://hg.mozilla.org/build/buildbot-configs/rev/60ab16f8a6d7

Comment 13

[Lukas Blakk [:lsblakk] use ?needinfo]

should see linuxqt builds go green now, ping if that is not the case (due to mozconfig path)

Comment 14

[Lukas Blakk [:lsblakk] use ?needinfo]

(In reply to comment #13)
> should see linuxqt builds go green now, ping if that is not the case (due to
> mozconfig path)

In fact, they still burn because linuxqt/ is not the path...need to chop off that 'qt' and look in linux/qt patch coming shortly

Comment 15

[Lukas Blakk [:lsblakk] use ?needinfo]

Attachment: fix2 for linuxqt mozconfig path

don't know if we will have qt on any other desktop platform so this hardcodes 'linux/' into the path, but I can manipulate the string another way if you prefer.

Comment 16

[Lukas Blakk [:lsblakk] use ?needinfo]

tests are going, builds are happening, so I'm calling this closed unless something else comes up that needs Releng attention.