ReleaseEngineering/How To/Setup a buildbot master: Difference between revisions

Jump to navigation Jump to search
add puppet verification steps
(update access rules to moved ftp.m.o)
(add puppet verification steps)
Line 82: Line 82:
== Final Verification ==
== Final Verification ==


We don't "burn in" buildbot masters - they will go directly to their assigned roles. The following steps should be performed to ensure the rest has worked okay:
We don't "burn in" buildbot masters - they will go directly to their assigned roles. The following steps should be performed to ensure the rest has worked okay(all steps should be run as user <tt>cltbld</tt>):


* SSH verification (and associated netflows).
* SSH verification (and associated netflows).
Line 96: Line 96:
     $ mysql -h buildbot-rw-vip.db.scl3.mozilla.com
     $ mysql -h buildbot-rw-vip.db.scl3.mozilla.com
     ERROR 1045 (28000): Access denied for user 'cltbld'@'10.22.70.209' (using password: NO)
     ERROR 1045 (28000): Access denied for user 'cltbld'@'10.22.70.209' (using password: NO)
</pre>
* puppet verification (check server, as well as running status)
<pre>
    [cltbld@buildbot-master35 ~]$ /sbin/chkconfig --list puppet
    puppet        0:off 1:off 2:on 3:on 4:on 5:on 6:off
    [cltbld@buildbot-master35 ~]$ ps $(pgrep puppet)
      PID TTY      STAT  TIME COMMAND
    20751 ?        Ssl    0:02 /usr/bin/ruby /usr/sbin/puppetd --server=master-puppet1.build.scl1.mozilla
    [cltbld@buildbot-master35 ~]$
</pre>
</pre>


= Personal / development masters =
= Personal / development masters =
See [[ReleaseEngineering/How To/Setup Personal Development Master]]
See [[ReleaseEngineering/How To/Setup Personal Development Master]]
Confirmed users
1,364

edits

Navigation menu