If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

Project branch request: projects/build-system

RESOLVED FIXED

Status

Release Engineering
General
P3
normal
RESOLVED FIXED
7 years ago
4 years ago

People

(Reporter: ted, Assigned: lsblakk)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [projectbranch])

Attachments

(1 attachment, 1 obsolete attachment)

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
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

7 years ago
/me suggests build-system
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.
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
Sure, let's go with that.
Summary: Project branch request: projects/build → Project branch request: projects/build-system

Updated

7 years ago
Assignee: nobody → lsblakk
Priority: -- → P3
Whiteboard: [projectbranch]
(Assignee)

Updated

7 years ago
Depends on: 633663
(Assignee)

Comment 6

7 years ago
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.
Depends on: 634821
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.
We don't seem to have unit tests from your pushes. Is that expected? My request did ask for unit tests.
(Assignee)

Updated

7 years ago
Depends on: 627454
(Assignee)

Comment 9

7 years ago
Created attachment 513185 [details] [diff] [review]
handling linuxqt mozconfigs

they are burning right now because of looking in nightly mozconfigs
Attachment #513185 - Flags: review?(catlee)
(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.
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.

Updated

7 years ago
Attachment #513185 - Flags: review?(catlee) → review+
Comment on attachment 513185 [details] [diff] [review]
handling linuxqt mozconfigs

landed http://hg.mozilla.org/build/buildbot-configs/rev/60ab16f8a6d7
Attachment #513185 - Flags: checked-in+
should see linuxqt builds go green now, ping if that is not the case (due to mozconfig path)
(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
Created attachment 513243 [details] [diff] [review]
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.
Attachment #513185 - Attachment is obsolete: true
Attachment #513243 - Flags: review?(catlee)

Updated

7 years ago
Attachment #513243 - Flags: review?(catlee) → review+
tests are going, builds are happening, so I'm calling this closed unless something else comes up that needs Releng attention.
Status: NEW → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → FIXED
Depends on: 635146
(Assignee)

Updated

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