engineyard /engineyard-jenkins
This project is deprecated in favour of eycloud-app-jenkins.
★ 28⑂ 6👁 109⑃ 2● 14▤ 0
TA的项目
+0
日增长
28
stars
6
forks
109
watchers
2
prs
14
issues
0
releases
README
DEPRECATED
This project is deprecated in favour of eycloud-app-jenkins.
Easier to do CI than not to.
Run your continuous integration (CI) tests against your Engine Yard AppCloud environments - the exact same configuration you are using in production!
You're developing on OS X or Windows, deploying to Engine Yard AppCloud (Gentoo/Linux), and you're running your CI on your local machine or a spare Ubuntu machine in the corner of the office, or ... you're not running CI at all?
It's a nightmare. It was for me.
But now, Jenkins CI, the jenkins CLI project, and engineyard-jenkins now make CI easier to do than not to for Engine Yard AppCloud users.
And here's some logos:
Installation
gem install engineyard-jenkins
This will also install the jenkins CLI to interact with your Jenkins CI from the command line.
Hosting on Engine Yard AppCloud
Using Engine Yard AppCloud "Quick Start" wizard, create an application with Git Repo git://github.com/engineyard/jenkins_holding_page.git (options: rails 3, passenger), and add your own SSH keys. This will create an environment called jenkins_server_production. Boot the environment as a Single instance (or Custom cluster with a single instance).
Optionally, though it is quite pretty, deploy/ship the jenkins_holding_page application and visit the HTTP link to see the remaining "Almost there..." instructions.
Finally, install Jenkins CI and rebuild the environment:
$ ey-jenkins install_server
When this completes, visit the URL or refresh the "Almost there..." page to see your Jenkins CI server.
Using the jenkins list CLI task you can also test there is a working server with no jobs:
For the Jenkins slaves' configuration, you'll need:
The jenkins_server_production instance public key:
$ ey ssh -e jenkins_server_production
cat /home/deploy/.ssh/id_rsa.pub
Do those steps, copy down the configuration and you're done! Now, you either visit your Jenkins CI site or use jenkins list to see the status of your projects being tested.
Hosting elsewhere
Hosting Jenkins CI on Engine Yard AppCloud is optional; yet delightfully simple. Jenkins CI can be hosted anywhere.
If you host your Jenkins CI elsewhere then you need the following information about your Jenkins CI environment to be able to add EngineYard AppCloud instances as Jenkins nodes/slaves:
Jenkins CI public host & port
Jenkins CI's user's public key (probably at /home/deploy/.ssh/id_rsa.pub)
Jenkins CI's user's private key path (probably /home/deploy/.ssh/id_rsa)
Running your CI tests on Engine Yard AppCloud
This is the exciting part - ensuring that your CI tests are being run in the same environment as your production applications. In this case, on Engine Yard AppCloud.
It is assumed that you already have a production application environment (might have multiple applications in it):
In the Engine Yard AppCloud UI, create another environment that matches the production environment exactly (same Ruby, same set of apTop issues
#10build fails installing linecache19 gem on a ruby 1.9 server3 comments · 2011-07-09#3Bundle not working with RVM2 comments · 2011-04-19#14EngineYard Server rebuild is removing plugins installed into Jenkins1 comments · 2012-02-23#1SSL support for hudson1 comments · 2011-01-21#16jasmine support for jenkins0 comments · 2012-09-24#13Dependency gems not installed automatically on EngineYard systems0 comments · 2012-02-20#12Fails to install server with collaborators0 comments · 2011-10-19#11Screenshots still say "hudson"0 comments · 2011-09-13