Converted HowToSetupBuildbotForMelange.md
diff --git a/HowToSetupBuildbotForMelange.wiki b/HowToSetupBuildbotForMelange.md
similarity index 92%
rename from HowToSetupBuildbotForMelange.wiki
rename to HowToSetupBuildbotForMelange.md
index aa044a5..450304a 100644
--- a/HowToSetupBuildbotForMelange.wiki
+++ b/HowToSetupBuildbotForMelange.md
@@ -1,13 +1,10 @@
-#summary This page documents how to setup a buildbot for Melange.
-#labels Contents-Review,Importance-Useful,Phase-Deploy
+# Introduction
-= Introduction =
+Buildbot is an open source framework for automating software build, test run, and release. At Melange, we're using buildbot for these automations. The instructions are for a user called "buildbot" on a mint clean debian based machine, however due to various choices made in this page, the instructions shouldn't be a lot different for other distros.
-Buildbot is an open source framework for automating software build, test run, and release. At Melange, we're using buildbot for these automations. The instructions are for a user called "buildbot" on a mint clean debian based machine, however due to various choices made in this page, the instructions shouldn't be a lot different for other distros.
+# Instructions
-= Instructions =
-
-{{{
+```
$ BASEDIR='/mnt/teraref'
$ wget https://raw.github.com/pypa/pip/master/contrib/get-pip.py
$ sudo python get-pip.py
@@ -33,33 +30,33 @@
$ cd $BASEDIR/buildbot/venv; buildslave create-slave slave localhost:9989 example-slave pass
$ buildslave start slave; tail -f slave/twistd.log
# Again, If the logs appear okay, we're good to go!
-}}}
+```
The next step involves copying the config files from `/configuration` directory in melange-project-root, to the buildbot machine's master folder - `$BASEDIR/buildbot/venv/master/`
-The file private.py has some fields, whose description is documented in the file itself. The fields are pretty straightforward, and the description about them in the same file should be sufficient.
+The file private.py has some fields, whose description is documented in the file itself. The fields are pretty straightforward, and the description about them in the same file should be sufficient.
-Now, let's restart the buildbot -
+Now, let's restart the buildbot -
-{{{
+```
$ cd $BASEDIR/buildbot/venv/master
$ buildbot restart
-}}}
+```
-At this point, it might make sense to run these commands, just to check everything is in order -
+At this point, it might make sense to run these commands, just to check everything is in order -
-{{{
+```
$ cd $BASEDIR/buildbot/venv
$ buildbot master start; tail -f master/twistd.log
$ buildslave start slave; tail -f slave/twistd.log
-}}}
+```
Next, we point our browser at the IP at which buildbot is hosted, and point our browser to port 8020. The waterfall page should appear. Try doing a force-build and see if the buildbot gives expected results.
-==How to enable buildbot to send emails?==
+## How to enable buildbot to send emails?
Now this is a bit tricky, since postfix can be hard to configure. But if you follow the below mentioned steps, things should go smoothly.
-{{{
+```
$ sudo apt-get install postfix mailutils libsasl2-2 ca-certificates libsasl2-modules
# Open the postfix config file.
@@ -96,7 +93,7 @@
# Point your browser to this URL, and authenticate.
# Next, try sending email again, and you should be good to go.
# Hooray!
-}}}
+```
Also, you might need to look at master.cfg of buildbot in order to decide for the value of a few parameters.
