Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(702)

Side by Side Diff: configs/chromium/slave/Makefile

Issue 648353002: Remove Skia's forked buildbot code (Closed) Base URL: https://skia.googlesource.com/buildbot.git@master
Patch Set: Address comment Created 6 years, 2 months ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View unified diff | Download patch
« no previous file with comments | « configs/chromium/master/slaves.cfg ('k') | configs/chromium/slave/buildbot.tac » ('j') | no next file with comments »
Toggle Intra-line Diffs ('i') | Expand Comments ('e') | Collapse Comments ('c') | Show Comments Hide Comments ('s')
OLDNEW
(Empty)
1 # -*- makefile -*-
2
3 # This is a simple makefile which lives in a buildmaster/buildslave
4 # directory (next to the buildbot.tac file). It allows you to start/stop the
5 # master or slave by doing 'make start' or 'make stop'.
6
7 # The 'reconfig' target will tell a buildmaster to reload its config file.
8
9 # Note that a relative PYTHONPATH entry is relative to the current directory.
10
11 # On the Mac, the buildbot is started via the launchd mechanism as a
12 # LaunchAgent to give the slave a proper Mac UI environment for tests. In
13 # order for this to work, the plist must be present and loaded by launchd, and
14 # the user must be logged in to the UI. The plist is loaded by launchd at user
15 # login (and the job may have been initially started at that time too). Our
16 # Mac build slaves are all set up this way, and have auto-login enabled, so
17 # "make start" should just work and do the right thing.
18 #
19 # When using launchd to start the job, it also needs to be used to stop the
20 # job. Otherwise, launchd might try to restart the job when stopped manually
21 # by SIGTERM. Using SIGHUP for reconfig is safe with launchd.
22 #
23 # Because it's possible to have more than one slave on a machine (for testing),
24 # this tests to make sure that the slave is in the known slave location,
25 # /b/slave, which is what the LaunchAgent operates on.
26 USE_LAUNCHD := \
27 $(shell [ -f ~/Library/LaunchAgents/org.chromium.buildbot.slave.plist ] && \
28 [ "$$(pwd -P)" = "/b/build/slave" ] && \
29 echo 1)
30
31 TOPLEVEL_DIR := $(shell pwd)/../../../third_party/chromium_buildbot
32 export PYTHONPATH=$(TOPLEVEL_DIR)/third_party/buildbot_7_12:$(TOPLEVEL_DIR)/thir d_party/twisted_8_1
33
34 # Note that initscripts and make can conspire to leave child processes with
35 # an unlimited maximum stack size. This causes the Linux kernel to use a
36 # strange VM layout.
37 # We therefore explicitly set a (typical) stack limit.
38 start:
39 ifneq ($(USE_LAUNCHD),1)
40 sh -c 'ulimit -s 8192; python run_slave.py --no_save -y buildbot.tac'
41 else
42 launchctl start org.chromium.buildbot.slave
43 endif
44
45 stop:
46 ifneq ($(USE_LAUNCHD),1)
47 if `test -f twistd.pid`; then kill `cat twistd.pid`; fi;
48 else
49 launchctl stop org.chromium.buildbot.slave
50 endif
51
52 reconfig:
53 kill -HUP `cat twistd.pid`
54
55 log:
56 tail -F twistd.log
57
58 wait:
59 while `test -f twistd.pid`; do sleep 1; done;
60
61 restart: stop wait start log
OLDNEW
« no previous file with comments | « configs/chromium/master/slaves.cfg ('k') | configs/chromium/slave/buildbot.tac » ('j') | no next file with comments »

Powered by Google App Engine
This is Rietveld 408576698