Closed Bug 413489 Opened 15 years ago Closed 15 years ago
.in patches on the try server
There was an e-mail sent to email@example.com today wondering about how to test configure.in changes on the try server. We require Autoconf 2.13 to do this; the slaves have it as 'autoconf-2.13'. By setting $AUTOCONF in the mozconfig files, we should be able to force it to use that version when re-generating configure. The only thing I'm unsure about is whether to put RUN_AUTOCONF_LOCALLY in the try server mozconfigs, or have people set that when they want it. Is there any disadvantage/risk in running it every time?
There is little/no risk in running it every time in clobber builds. In depend builds it's likely to trigger a world-rebuild more often than necessary. But since the tryserver builds are always clobber, you should be able to set it safely.
I've tested these new mozconfigs on the try server slaves, they should be fine.
Attachment #298730 - Flags: review?(rhelmer)
Attachment #298730 - Flags: review?(rhelmer) → review+
Comment on attachment 298730 [details] [diff] [review] [checked in] always regenerate configure on the try server, to support configure.in patches Checking in mozconfig-linux; /cvsroot/mozilla/tools/buildbot-configs/tryserver/mozconfig-linux,v <-- mozconfig-linux new revision: 1.2; previous revision: 1.1 done Checking in mozconfig-mac; /cvsroot/mozilla/tools/buildbot-configs/tryserver/mozconfig-mac,v <-- mozconfig-mac new revision: 1.2; previous revision: 1.1 done Checking in mozconfig-win32; /cvsroot/mozilla/tools/buildbot-configs/tryserver/mozconfig-win32,v <-- mozconfig-win32 new revision: 1.2; previous revision: 1.1 done
Attachment #298730 - Attachment description: always regenerate configure on the try server, to support configure.in patches → [checked in] always regenerate configure on the try server, to support configure.in patches
Hey Peter, configure.in changes should be supported now. Can you give it another try when you get a chance?
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Will do that, thanks Ben!
Yes, this works fine now. I see Generating /builds/buildbot/sendchange-slave/sendchange-linux/mozilla/configure using autoconf cd /builds/buildbot/sendchange-slave/sendchange-linux/mozilla; /usr/local/bin/autoconf-2.13 make: Entering directory `/builds/buildbot/sendchange-slave/sendchange-linux/mozilla' Generating /builds/buildbot/sendchange-slave/sendchange-linux/mozilla/nsprpub/configure using autoconf cd /builds/buildbot/sendchange-slave/sendchange-linux/mozilla/nsprpub; /usr/local/bin/autoconf-2.13 cd /builds/buildbot/sendchange-slave/sendchange-linux/mozilla/objdir /builds/buildbot/sendchange-slave/sendchange-linux/mozilla/configure in the logs of the Linux machine, and similar for Mac and Windows, too.
Status: RESOLVED → VERIFIED
Moving try server bugs to the new component.
Component: Build & Release → Try Server
Product: mozilla.org → Webtools
QA Contact: build → try-server
Component: Try Server → Release Engineering
Product: Webtools → mozilla.org
QA Contact: try-server → release
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.