Closed Bug 746004 Opened 12 years ago Closed 9 years ago

Need a reasonable way to trigger builds with clang on Try

Categories

(Release Engineering :: General, defect)

Product:
Release Engineering
Component:
General
Platform:
x86_64
Linux
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: hub, Unassigned)

Details

Current we can't seem to be able to push to try server and have a build done with clang. But yet we get people comlaining of breakage with clang.

We need to have a build option to build with clang.
Component: Tinderbox → Release Engineering
Product: Webtools → mozilla.org
QA Contact: tinderbox → release
Version: Trunk → other
Rafael has been working on clang for some time, including doing try builds.
Yes, we have clang on the bots. The process for getting them there is very arcane, but doable. Look at

https://bugzilla.mozilla.org/show_bug.cgi?id=743704

for example.
Heh. So the way to build with clang on Try is

* check http://hg.mozilla.org/build/puppet-manifests/file/tip/modules/packages/manifests/devtools.pp to determine the currently installed version and thus the path to it

* iteratively learn what things to disable in the various mozconfigs, like PGO and ccache and maybe warnings as errors depending on how we're doing at the moment

* set CC and CXX
Component: Release Engineering → Release Engineering: Developer Tools
QA Contact: release → lsblakk
Summary: Need buildbot using clang → Need a reasonable way to trigger builds with clang on Try
Can we consider this fixed now that we have tooltool?
Truly fixed would be "try: -b do -p a -c clang", but let's charitably say it would be fixed with a not-too-crazy set of instructions in https://wiki.mozilla.org/ReleaseEngineering/TryServer#How_to_get_clang_builds

What would those instructions currently say? Something like:

1. Edit every Linux and Mac mozconfig in the tree, removing --enable-warnings-as-errors, --with-ccache, and PROFILE_GEN_SCRIPT.
2. ??? the tooltool-manifests to ??? based on ???
3. Edit build/macosx/common and build/unix/mozconfig.linux to change CC and CXX to point to clang

Basically, it's exactly like it was in April - "load https://tbpl.mozilla.org/?tree=Try&pusher=respindola@mozilla.com and keep going backward until you find one that looks like a 'build with clang' push and copy that."
QA Contact: lsblakk → hwine
Product: mozilla.org → Release Engineering
Probably fixed at some point? Please re-open if this is still useful.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Component: Tools → General
You need to log in before you can comment on or make changes to this bug.