diff options
| author | Paul Sokolovsky <paul.sokolovsky@linaro.org> | 2011-06-17 15:55:29 +0300 |
|---|---|---|
| committer | Paul Sokolovsky <paul.sokolovsky@linaro.org> | 2011-06-17 15:55:29 +0300 |
| commit | 65aefdc86d2a6d968d3c9af3ca55b68cf4dee22a (patch) | |
| tree | 6061f39e32c7e8e950f6081fecbd681277fc09cc /README | |
| parent | aa5ddd314f1c7b24a637d3b43d54b5f793eb13f3 (diff) | |
Ask to change admin password.
Diffstat (limited to 'README')
| -rw-r--r-- | README | 26 |
1 files changed, 14 insertions, 12 deletions
@@ -45,27 +45,29 @@ cd linaro-android-build-tools/control This will create complete Cloud Buildd setup, you just need to fill in EC2 credentials which will be used to create build slave instances. -Open URL as output when 'sandbox-create' script finished in the browser, -append "/jenkins". Login as username: admin, password: admin. Go to -"Manage Jenkins" -> "Configure System". Search for "Access Key ID", -"Secret Access Key" and fill in EC2 credentials. Now you need to create -keypair which Jenkins will use to create slave instances, this supposed to -be automated by clicking on "Generate Key", but does not work in latest -Jenkins versions, so instead run: +1. Open URL as output when 'sandbox-create' script finished in the browser, + append "/jenkins". +2. Login as username: admin, password: admin. +3. Go to "People" -> "Jenkins Admin" -> "Configure". Change password. +4. Go to "Manage Jenkins" -> "Configure System". Search for "Access Key ID", + "Secret Access Key" and fill in EC2 credentials. +5. Now you need to create keypair which Jenkins will use to create slave + instances, this supposed to be automated by clicking on "Generate Key", + but does not work in latest Jenkins versions, so instead run: -ec2-add-keypair jenkins@cloud-buildd >jenkins@cloud-buildd.rsa + ec2-add-keypair jenkins@cloud-buildd >jenkins@cloud-buildd.rsa -Paste contents of jenkins@cloud-buildd.rsa into "EC2 RSA Private Key". Click -"Test Connection" and ensure you get "SUCCESS". + Paste contents of jenkins@cloud-buildd.rsa into "EC2 RSA Private Key". +6. Click "Test Connection" and ensure you get "SUCCESS". In addittion to fully automated sandbox-create script which takes care of instance creation for master node, there're following scripts with narrower scope: - control/setup-control-node-via-ssh <hostname> + control/setup-control-node-via-ssh <hostname> * This will set up existing instance/physical host as Cloud Buildd master node - control/setup-control-node + control/setup-control-node * This will set up Cloud Buildd control node on the current host, which should be a blank, freshly installed host/instance running Ubuntu Server 10.10 or 11.04. |