You can access it from here: http://ci.budabot.com/ (thx for CaptainZero for setting up the ci.-domain).
The server is located on my linux machine so if you encounter problems with it, complain to me.
The CI server is a service which checks Budabot's repository for new commits and executes jobs if new commits are made into it. It can also run jobs periodically.
Currently there are three jobs configured:
- Generation of API documentation: Every 15 minutes, if new commits are made it generates API documentation from trunk using ApiGen and uploads the documentation to Tyrence's server at http://budabot.jkbff.com/api/ using command phing -propertyfile $JENKINS_HOME/budabot-ci-phing.properties apidoc+upload.
- Generation of wiki documentation: Every 15 minutes, if new commits are made it generates API documentation of a select few classes in wiki format using command phing -propertyfile $JENKINS_HOME/budabot-ci-phing.properties wikidoc and commits them to our wiki with command svn commit --username ci.budabot --message "CI: Updated wiki documentation." wiki. Converts for example trunk's AccessLevel class in to ApiAccessLevel wiki page.
- Building of release archive: Every 15 minutes, if new commits are made it will generate a release archive and upload it to Tyrence's server at http://budabot.jkbff.com/builds/ using command (in trunk) phing -propertyfile $JENKINS_HOME/budabot-ci-phing.properties build+upload.
The budabot-ci-phing.properties file in the commands above is a collection of properties with following contents:
Code: Select all
apidoc.upload_destination=<www-root's local path on jkbff server>/api/
build.upload_destination=<www-root's local path on jkbff server>/builds/
If you come up with any other ideas what should be automated, please post here or bug me in IRC.