-
Notifications
You must be signed in to change notification settings - Fork 1
Scenario of setting up a project with Buildbot Master + Sqlite Slave
You need to create virtualenvwrapper.
$ mkvirtualenv proteus-deploy-user
$ pip install git+git://github.com/Proteus-tech/deploy.git@develop
$ pip freeze
If you find Django==1.4 and proteus-deploy==0.0.7 in your environment, then everything is good! Now you can start a new project
=====================
$ startproject hobby
Then you can commit your code into the repository.
$ start-simple-server proteus
A new instance is created. You can find the host name of the created EC2 instance on the terminal.
$ complete_master_config <e2_host> <repository>
This would edit buildbot_config/settings.py, adding a host of the buildbot and repository URL into the settings file.
Commit you changes into the repository.
$ setup-buildbot-on-server proteus <ec2_host> hobby git://github.com/juacompe/hobby.git
Done! The buildbot can be accessed at http://<ec2_host>:8010/
=====================
$ startproject hobby
Then you can commit your code into the repository.
$ start-simple-server proteus
A new instance is created. You can find the host name of the created EC2 instance on the terminal.
$ complete_master_config <e2_host> <repository>
This would edit buildbot_config/settings.py, adding a host of the buildbot and repository URL into the settings file.
Commit you changes into the repository.
$ setup-buildbot-svn-on-server proteus <ec2_host> hobby
Done! The buildbot can be accessed at http://<ec2_host>:8010/
=====================
$ ssh ubuntu@<ec2_host>
$ ps -ef | grep build
If you find buildbot start and buildslave start, then Buildbot is working.
You can force build for checking Buildbot checkouts code from repository
http://<ec2_host>:8010/builders/builder-sqlite
And see waterfall at
http://<ec2_host>:8010/waterfall
If correct, builder-sqlite's waterfall will be green.