The message is clear enough, so open the configuration again, fix the error, and reconfig the master.ġ.4.1. Luckily, the Buildbot master will ignore the wrong configuration and keep running with the previous configuration. This time, it’s clear that there was a mistake in the configuration. Please inspect the master.cfg file for errors,Ĭorrect them, then try 'buildbot reconfig' again. 18:40:46+0000 reconfig aborted without making any changes 18:40:46+0000 error while parsing config file: EOL while scanning string literal (master.cfg, line 103) (traceback in logfile) Return _inlineCallbacks(None, gen, Deferred())įile "/usr/local/lib/python2.7/dist-packages/twisted/internet/defer.py", line 1128, in _inlineCallbacksįile "/usr/local/lib/python2.7/dist-packages/buildbot/master.py", line 289, in doReconfigįile "/usr/local/lib/python2.7/dist-packages/buildbot/config.py", line 156, in loadConfigĮxceptions.Synta圎rror: EOL while scanning string literal (master.cfg, line 103) 18:40:46+0000 error while parsing config file:įile "/usr/local/lib/python2.7/dist-packages/buildbot/master.py", line 265, in reconfigįile "/usr/local/lib/python2.7/dist-packages/twisted/internet/defer.py", line 1274, in unwindGenerator 18:40:46+0000 Loading configuration from '/data/buildbot/master/master.cfg'
18:40:46+0000 beginning configuration update Now, if you go back to the waterfall page, you will see that the project’s name is whatever you may have changed it to, and when you click on the URL of the project name at the bottom of the page, it should take you to the link you put in the configuration. The important lines are the ones telling you that the new configuration is being loaded (at the top) and that the update is complete (at the bottom).
Reconfiguration appears to have completed successfully. 10:11:09-0600 configuration update complete 10:11:09-0600 GitPoller repository already exists 10:11:09-0600 gitpoller: using workdir '/path/to/buildbot/gitpoller-workdir' 10:11:09-0600 adding 1 new changesources, removing 1 10:11:09-0600 removing 0 old schedulers, updating 0, and adding 0 10:11:09-0600 builder runtests is unchanged 10:11:09-0600 configuration update started 10:11:09-0600 loading configuration from /path/to/buildbot/master.cfg Let’s step it up a little in the second tutorial by changing the configuration and doing an actual build. You’ve got a taste now, but you’re probably curious for more. It’s easy to take your first steps, but this is about as far as we can go without touching the configuration. We just wanted to get you to dip your toes in the water. In the next section, we’ll see how to manually start a build.
Your master is now quietly waiting for new commits to hello-world. You should now be able to go to where you will see a web page similar to:Ĭlick on “Builds” at the left to open the submenu and then Builders to see that the worker you just started (identified by the green bubble) has connected to the master: 15:56:51+0100 Got workerinfo from 'example-worker' 15:56:51+0100 worker 'example-worker' attaching from Release Notes for Buildbot 0.9.9.post1 ( ) Release Notes for Buildbot 0.9.9.post2 ( ) Release Notes for Buildbot 0.9.12.post1 ( ) Release Notes for Buildbot 0.9.15.post1 ( )